As I moved from project to project I noticed, without fail, one process was always used. It didn't matter who the client was, how long the timeline was or how small/large the team was. Methodology was expected and followed. There was never a point in time where we just went ahead and dived in because, what I realized ultimately was, without planning how would the team even have a good grasp of what the tasks were? Even if the team did - who did what,when, and how? I've used many different methodologies across numerous projects and have streamlined it to these essential steps:
.png)
This diagram shows the essential steps (depending on project steps can be added, e.g. Deploy)
Plan/Analyze: Develop a timeline, determine key stakeholders, analyze requirements, determine scope and plan key activities
Design: Consists heavily of documenting, prototyping based on requirements, current needs, and future needs. This is where business requirements documents, functional requirements documents, technical requirements documents, product requirements documents are built.
Build: Development based on documentation and discussions, a lot of configuration, a lot of programming and a ton of back and forth between groups.
Test: Critical to test to make sure the product aligns to the design and needs.
One thing I noticed is these steps are generally iterative, it's never step A to step B. Sometimes you will be building -> testing -> building -> testing -> designing -> building -> testing, until everything comes together as expected. Every step is critical to ensure that the end product aligns to the end goal.
.png)
This diagram shows the essential steps (depending on project steps can be added, e.g. Deploy)
Plan/Analyze: Develop a timeline, determine key stakeholders, analyze requirements, determine scope and plan key activities
Design: Consists heavily of documenting, prototyping based on requirements, current needs, and future needs. This is where business requirements documents, functional requirements documents, technical requirements documents, product requirements documents are built.
Build: Development based on documentation and discussions, a lot of configuration, a lot of programming and a ton of back and forth between groups.
Test: Critical to test to make sure the product aligns to the design and needs.
One thing I noticed is these steps are generally iterative, it's never step A to step B. Sometimes you will be building -> testing -> building -> testing -> designing -> building -> testing, until everything comes together as expected. Every step is critical to ensure that the end product aligns to the end goal.
No comments:
Post a Comment