Typical Projects with the paraphernalia of sequences and steps are PUSHed into waterfall development methodologies. Project managers and stakeholders insist so much on process frame works, documentation and client sign-offs at every phase like Business Requirements, Software requirements, LLD, HLDs, Code check-ins, testing etc leading to heavy overheads. Not only does this create wastes in the system, it causes potential defects waiting to be discovered during the downstream stages of product releases. This is the way to “how to make projects fail and increase cost”.
Instead if project stakeholders commit to Agile Development, build products collaboratively and value people who matter most like developer, user and other key stakeholders and have trust in the system being built, the aim – the goal of successful products release will be achieved in the end. Means are important for sure, not to the extent of impeding the aim – “building products quicker and better”.
Product owner and scrum master jointly can decide on priorities based on drive the product development towards success.
- Have Product Vision.
- Collaborate with Customers.
- Believe in people who build products.
- Use optimum process as a means.
- PULL the Value through customer driven development.
- Eliminate Waste.
- Make Great Products.
Wisdom of Albert Einstein:
“A perfection of means, and confusion of aims, seems to be our main problem”.
Filed under: Albert Einstein