THE IMPORTANCE OF CLEAR REQUIREMENTS - CAKE MAKING, RECIPE AND INGREDIENTS
I was in a project meeting recently and we had this conversation, arising from many different inputs and opinions about the end-product.
It’s like a cake: We think that we have agreed that we want to bake a series of cakes, but we have:
Different ideas of what the cake should look like
What ingredients it should have in it
What order those ingredients should go in to the mix
How long it takes and costs to prep and bake the cake
How far we can go without having the full ingredients
What happens if we bake the cake, without agreeing the ingredients to the end result and taste
This is such a great metaphor for Project and Change Management. It is always important to be clear on goals, deliverables and their attributes up-front.
Waterfall (PRINCE2) and Agile (Scrum) are two distinct project management approaches with different methodologies and philosophies. However, they share a common factor in emphasizing clarity on the end-product. Here's a summary of the differences between Waterfall and Agile projects:
WATERFALL (PRINCE2):
Sequential and linear: Waterfall follows a sequential approach where each phase is completed before moving on to the next one. It has predefined stages like requirements gathering, design, development, testing, and deployment.
Detailed planning: Waterfall projects require comprehensive upfront planning, including defining scope, setting timelines, and determining resources.
Rigid and inflexible: Once a phase is completed, it is challenging to go back and make changes without affecting subsequent stages.
Documentation-heavy: Waterfall projects emphasize extensive documentation, including detailed requirements, specifications, and project plans.
Limited customer involvement: Customers' involvement typically occurs at the beginning and end of the project, with less collaboration during the development process.
AGILE (SCRUM):
Iterative and incremental: Agile projects are divided into short iterations called sprints, usually lasting a few weeks. Each sprint produces a usable and potentially shippable product increment.
Adaptive and flexible: Agile allows for changes and refinements throughout the project, enabling teams to respond to evolving requirements and market conditions.
Continuous feedback: Regular feedback loops are established with stakeholders, ensuring continuous communication and alignment of expectations.
Self-organizing teams: Agile projects rely on self-managed teams that collaborate closely, make decisions collectively, and are empowered to adapt and respond to challenges.
Emphasis on value delivery: Agile prioritizes delivering value to the customer early and frequently, focusing on the highest-priority features first.
COMMON FACTOR:
Clarity on the end-product: Both Waterfall and Agile projects require a clear understanding of the end-product or project goals. The vision and objectives need to be well-defined and communicated to ensure alignment among stakeholders and guide the development process. Clarity on the end-product helps in determining project scope, making informed decisions, and evaluating success criteria.
IF IT IS NOT WRITTEN DOWN
If it is not written down how to we know? If it is not written down did it happen? If it is not written down how can you test or evaluate? If it is not written down how can you be sure? If it isn't written down properly, you're not sure exactly what happened. If the records are not correct, neither is the product.
Tim HJ Rogers
Adapt Consulting Company
We support people and organisations with Processes, Projects and Change
https://www.linkedin.com/company/adapt-consulting-company
Tim@AdaptConsultingCompany.com
Mob 447797762051
https://www.linkedin.com/in/timhjrogers/
#people #process #performance #projects #programmes #pmo #change #processimprovement #projectmanagement #changemanagement #workshops #mediation #coach #icfcoach #mentor #facilitation #training #jersey #channelislands
No comments:
Post a Comment