Scrum Team Asks... Should We Use a Different Methodology? What about Waterfall or Lean or Kanban?
Different types of projects can be easier to manage with different methodologies. Some teams or companies do mix and match. However, team members may be confused on expectations if they are not familiar with the methodology being used. Each method has its own philosophy and value system, schedule, and hierarchy so its more complicated for team members than just completing their tasks in a timely manner. So if a different methodology is introduced for part of the project, it would be ideal to have some training and clear communication.
Take a look at these different approaches. It may become clear why your team or industry prefers a certain approach. Perhaps at your company, a different team has a lot of success with an approach that fits their team's goals or department.
Waterfall (Traditional) Approach
Linear approach with ordered steps, good for physical engineering disciplines. Many different types of waterfall are available for different types of projects and industry. Good for projects that have to be done in a certain order, when goals are not likely to change, or where there is a tight budget.
Waterfall Key Takeaways:
- Project managers take an active lead by assigning specific tasks to team members.
- Scope and cost are clearly defined at the beginning of the project, and changes go through a formal request process.
- The Schedule is linear, with one step following another. Initiating, planning, executing, and closing phases flow like a waterfall to the next phase until the project is completed.
- Milestones are presented in large chunks to the stakeholders.
Agile Approach
Faster delivery of products, software products. More of a mindset that just steps, regular feedback approach. Product can be launched before completed. Instead of a project manager, a Scrum master acts as a facilitator for the team and the team manages their own work.
Agile/Scrum Key Takeaways:
- Scrum master acts as a facilitator and removes barriers from the project so that the team can focus on completing their tasks is a self-managing framework.
- The scope is flexible, or agile, based on feedback from stakeholders and focuses on giving value quickly and in small, regular increments.
- The schedule is broken into Sprint phases and has a list of deliverables selected from a product backlog.
- The cost and schedule can change as the scope changes.
- Stakeholders give on going feedback on the product about the quality, scope, etc
- Communication between the team and the stakeholders is frequent, as stakeholders make decisions throughout the project.
Lean Six Sigma
Uses DMAIC framework to define the goal, measure, analyze, improve and control a business problem.
Lean Six Sigma focuses on data: how to measure current processes data, measure the data by a reporting system, analyze data in reports by looking for gaps and issues to find out what to improve, and making improvements after careful analysis, and controlling to put new documentation and processes in place.
Lean Six Sigma Key Takeaways:
- Can be used to solve any business problem.
- Helps discover best practices.
- Commonly used to save money, reduce waste, and improve quality,
- Framework values a positive work environment and team collaboration.
