Does this sound familiar? You, or your developers have completed development for a feature. Its demonstrated to a stakeholder, who identifies some changes that need to be made before release. Not only does it require undoing of work that has already been coded and tested, the developers feel frustrated and it will cost time, and ultimately more money.
So we’d like to share three tips, that when implemented successfully can help to avoid rework. And if you’d like to learn more about how these and other approaches could help avoid unnecessary cost and time in your team, please Contact Us.
Tip 1: Ensure that everyone is on the same page
Its common for different stakeholders to have varying assumptions about how something might work, be implemented and about how much time might be needed to complete it. Communicate and validate the look and feel, behaviour and use example usage scenarios at the start and during development, to ensure that as far as possible everyone has a common understanding.
Tip 2: Flag the ‘devil in the detail’ as soon as possible
Even after time is spent gaining a common understanding of how a feature will work and be implemented, there’s often issues that arise as the work progresses because of something previously unknown. Anything unknown with how a feature is implemented is a risk, so aim to identify the risks and how to mitigate these as early as possible during development of a feature. And communicate anything that may impact the common understanding of how the feature will work as soon as possible.
Tip 3: Seek feedback early and often
Its always possible that as a feature is implemented and partially working with test data, something arises that then requires change. Show progress on the feature regularly to decision makers as a means to confirm that the implementation is still in line with the common understanding and to identify any differences as soon as possible.
Dependent on your team, location and any other responsibilities they also have, there will be multiple ways to adopt these practices. Adopting a simple change and then reviewing its effectiveness is the way we typically recommend to implement such practices. To learn more about about how these might work for your specific team and working environment, please Contact Us.