When we’re unsure of what to test, the project might be at 𝑟𝑖𝑠𝑘 𝑜𝑓 𝑓𝑎𝑖𝑙𝑢𝑟𝑒.
Tests turn our client’s ideas into 𝘶𝘯𝘦𝘲𝘶𝘪𝘷𝘰𝘤𝘢𝘭 specifications. If we can’t write tests, we’re lost on what we need to program.
(1/10)
Tests turn our client’s ideas into 𝘶𝘯𝘦𝘲𝘶𝘪𝘷𝘰𝘤𝘢𝘭 specifications. If we can’t write tests, we’re lost on what we need to program.
(1/10)
𝗧𝗵𝗮𝘁’𝘀 𝗮 𝗳𝗮𝘀𝘁 𝘁𝗿𝗮𝗰𝗸 𝘁𝗼 𝗱𝗶𝘀𝗮𝘀𝘁𝗲𝗿.
We might think it’s the client’s fault. After all, we’re unable to write tests because requirements are vague and volatile.
But pointing fingers never solved any problems.
(2/10)
We might think it’s the client’s fault. After all, we’re unable to write tests because requirements are vague and volatile.
But pointing fingers never solved any problems.
(2/10)
So what can we do?
𝗔 𝗿𝗲𝗮𝗹𝗹𝘆 𝗲𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆 𝗶𝘀 𝘁𝗼 𝗿𝗲𝗱𝘂𝗰𝗲 𝘁𝗵𝗲 𝘀𝗰𝗼𝗽𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗰𝘂𝗿𝗿𝗲𝗻𝘁 𝗿𝗲𝗹𝗲𝗮𝘀𝗲.
(3/10)
𝗔 𝗿𝗲𝗮𝗹𝗹𝘆 𝗲𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆 𝗶𝘀 𝘁𝗼 𝗿𝗲𝗱𝘂𝗰𝗲 𝘁𝗵𝗲 𝘀𝗰𝗼𝗽𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗰𝘂𝗿𝗿𝗲𝗻𝘁 𝗿𝗲𝗹𝗲𝗮𝘀𝗲.
(3/10)
Smaller deliverables mitigate two common reasons for failure to clarify what software should do:
1. Trying to discuss 𝘵𝘰𝘰 𝘮𝘢𝘯𝘺 𝘧𝘦𝘢𝘵𝘶𝘳𝘦𝘴 at once.
2. 𝘐𝘯𝘴𝘦𝘤𝘶𝘳𝘪𝘵𝘺 on what the application has to offer to succeed.
(4/10)
1. Trying to discuss 𝘵𝘰𝘰 𝘮𝘢𝘯𝘺 𝘧𝘦𝘢𝘵𝘶𝘳𝘦𝘴 at once.
2. 𝘐𝘯𝘴𝘦𝘤𝘶𝘳𝘪𝘵𝘺 on what the application has to offer to succeed.
(4/10)
A narrower scope means we have less to focus on at once. So there’s more time and energy to dig deeper and define concrete requirements to guide our acceptance tests.
(5/10)
(5/10)
With less to develop, we can ship faster. Thus, get 𝑓𝑒𝑒𝑑𝑏𝑎𝑐𝑘 from the market sooner. That will shed light on what the app should do to satisfy users.
(6/10)
(6/10)
As programmers, it’s easy to disregard deliverables as a project manager’s responsibility.
(7/10)
(7/10)
However, it’s we that 𝘧𝘪𝘯𝘥 gaps in the specifications.
If we stay silent, no one will know misunderstandings exist until the project is delivered.
𝗧𝗵𝗮𝘁 𝗺𝗮𝘆 𝗯𝗲 𝘁𝗼𝗼 𝗹𝗮𝘁𝗲.
(8/10)
If we stay silent, no one will know misunderstandings exist until the project is delivered.
𝗧𝗵𝗮𝘁 𝗺𝗮𝘆 𝗯𝗲 𝘁𝗼𝗼 𝗹𝗮𝘁𝗲.
(8/10)
Even when we believe management will turn a deaf ear, let’s speak up. We might end up saving the project.
(9/10)
(9/10)
If you liked this thread, please do share it. I’d appreciate it :)
(10/10)
(10/10)