Procedure for Project Execution
Let's summarise what we learnt so far
The little time and money spent following the discovery workshop will be a big favour to yourself once you comprehend the long-term benefits. The Discovery Workshop is necessary for any project involving software development or mobile app development since it provides the following benefits:
Waterfall Method
For Constrained Budget
Very precise scope and a solid set of criteria that are unlikely to change over the project
Agile Scrum
For Evolving Scope/Hired Team
The scope is stated extremely short, and the requirements are very likely to change over the project.
How to Engage?
Which is better: Waterfall or Agile? The best method for you!
Engaging with Waterfall Method
Analysis
Product Owner
Project Manager
Business Analyst
CTO
Design
System Architect
UI/UX Designerr
Development
Front-end Developer
Back-end Developer
Testing
Solution Architect
QA Engineer
Tester
Devops
Analysis
Data Administrator
DevOpsr
Maintenance
Users
Testers
Support Manager
The waterfall technique is divided into linear, consecutive phases, with each step reliant on the deliverables of the preceding phase of your project. A project’s lifespan may be broken down into five stages using this method: discovery, definition, design, development, and delivery.
To determine whether your project comes under Waterfall Project Management, you must consider assumptions about the project, project limitations, the project objective, its business needs, and the project acceptance criteria, among other things. If all of these elements are properly defined and measurable, the waterfall method is appropriate for your project.
Because your project will have relatively defined features and functionality, A software requirement document (SRS) will be laid out to describe expectations and scope of the project which will be used till the final handoff of the project.
What if my requirements evolve?
Because your project’s features and functionality will be relatively defined, a software requirement document (SRS) will be created to explain the project’s expectations and scope, which will be used until the project’s final handoff.
Furthermore, we take the time to plan out the various components of a project before execution, but things are bound to alter as time goes on. ‘Change is the only constant’ in a project. As a result, we have put in place a framework to manage these adjustments. We assess the impact of changes on the existing scope and compute the time and cost associated with the adjustments. Finally, we ensure that the SRS document is kept up to date.
The Waterfall Procedure continues as intended, with a Quality Assurance Process at the conclusion to ensure that our project deliverables match the planned or changed scope of the project.
Use Cases: The Waterfall Approach
Stability
Has a highly clear scope and a solid set of criteria that are unlikely to change over the project
Predictability
Can create clear long-term milestones and monitor progress based on periodic deliverables.
Development Ready
Because the product owner must focus on the business aspect of the endeavour, he or she has less time to spend with the development team.
Strict Budget
Budget constraints with key features that cannot be compromised.
Using the Agile SCRUM Method
Continuous Iteration. Quicker Risk Mitigation
SCRUM is an Agile project management style that involves continuous iteration of development and testing throughout the software development lifecycle process. Unlike the Waterfall methodology, both development and testing are done concurrently.
Agile Vs Waterfall
When does Agile Project Execution Model Work?
- A product necessitates iterative development and teamwork.
- A product requires a faster risk mitigation strategy or a “fail-early” approach to development.
- Quality, cost, and time for developing the product are crucial constants with flexible and changeable requirements.
Roles in SCRUM
Deliverables in Agile Method
Product Backlog
This is usually done in the form of user stories. The product owner creates it. The product client's vision for the product is drafted here.
Release Backlog
The SCRUM master creates the release backlog by taking the product backlog and converting it into a list of tasks that will be issued in stages.
Sprint Backlog
This is being worked on in partnership with the team. The release backlog is taken and divided into one or two week sprints.
Defect Backlog
The problem backlog comprises a list of defects discovered throughout the one to two week sprint. These flaws are addressed immediately, which is required for a project to be deemed complete.
Agile Meetings
Use Cases: Agile SCRUM Methodology
Short Team Goals
Clear short-term milestones and periodic reviews of the progress.
Iterative Development
More time to spend with the development team by communicating clear objectives and targets so that they are always in sync with the project manager.
Feature Inspection
Many tries of a specific feature and fine-tuning of the feature by inspecting all of the pieces.
Sprint Planning
The client demands prompt and regular opportunities to examine the product and make judgements and adjustments to the project.
Continuous Reviews
It is necessary to perform regressive iterations throughout the testing process.
In the field of project management, there are two schools of thought: Agile and Waterfall. The appropriate project execution process, whether Waterfall or Agile, is determined by the context of your project. As we constantly say, each project is unique and necessitates a unique approach.
Agile technique, contrary to popular assumption, does not work with all sorts of projects. For example, suppose you operate a grocery store that is doing well and you want to open another one. You do not require a ‘Agile’ approach to project management. It would just be a waste of critical resources that are already in short supply. We assist our clients in determining whether they require Agile approach based on the level of uncertainty, value proposition, operational and value risks involved.
In a comparable manner the Waterfall technique, sometimes known as the ‘conventional’ style of project management, is employed for higher ‘quality’ standards due to its tight documentation and ‘assembly line’ production elements. That is not totally correct, because ‘Quality’ is context-dependent. Quality can be built into Agile projects just as easily as it can into Waterfall initiatives. Waterfall projects, like Agile initiatives, can have poor quality.
