Applying both Agile and Waterfall in one project

  • 2,763 views
Uploaded on

Agile is gathering momentum but its not easy to switch to Agile especially in complex environments like banking or multinationals. Many companies can’t refuse Waterfall but understand the value of …

Agile is gathering momentum but its not easy to switch to Agile especially in complex environments like banking or multinationals. Many companies can’t refuse Waterfall but understand the value of Agile and want to start applying it. How to combine Waterfall and Agile in one project, do it effectively and get value? In every standard Waterfall phase from initiation till closure Agile is able to help Project manager, team and stakeholders be more effective, adaptive, meet end user expectations better and have a fun. There are cases from CISCO Systems, NASA, US health care program to learn from.

I want to demonstrate that it is possible and often necessary to combine both Waterfall and Agile in one project. We will review challenges of big complex environments that have absorbed Waterfall and have strict procedures and guidelines but are willing to gradually move to Agile.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
2,763
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
158
Comments
1
Likes
5

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Applying both Agile and Waterfall in one project Maksym Dovgopolyi, PMP, CSM Geneva, SoftShake 2013 Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 2. What We Will Cover Today: ● Why apply Agile in Waterfall Project ● How and when to apply Agile ● Model of mixed project ● Factors of successfully applied Agile ● Growing of Agile mindset ● Why applying Agile may fail Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 3. Agile in Cisco Systems 2009. ● Cisco produces switches and routers using mainly Waterfall; ● New projects in software development; ● Needs to deliver fast and acquire visibility and credibility. Problems to face ● ● ● ● Cisco was mainly using Waterfall; Need to gain credibility; ISO and TL 9000 certifications; Perception: “Agile if for dirty and quick work”. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 4. Agile in Cisco Systems Decisions ● ● ● ● ● ● ● Work directly with the business units (customers) to figure out what they need; Regular demonstration of products to the project stakeholders; Welcome changes and quick respond to the customer during the release; Use scrum; Bet on testing and prototyping; Adapt and improve internal processes; Interaction with Waterfall/ Results ● ● ● ● Delivered working software quickly and gained Agile approach credibility within the company; Agile team grown from 6 to 26 people in 2 years; Cisco passed an ISO-9000 audit; Cisco now officially supports both Agile and Waterfall and has processes for both methodologies. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 5. When to Use Agile and Waterfall Waterfall Agile ● Requirements are very well known; ● Product definition is stable; ● Technology is understood; ● New version of an existing product; ● Integration an existing product to the new platform; ● Project is large, expensive, complicated. ● Business objectives are well defined; ● Functionality of the system is clearly visible; ● End-users are involved; ● Team is stable and skilled; ● Input data for the project already exists (JIT); ● Tech requirements are reasonable and well within the capabilities of the technology being used; ● System can be modularized. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 6. Why apply Agile in Waterfall Project? Avoid weaknesses of Waterfall approach and bring strength of Agile approach: ● ● ● ● ● ● Better control of budget and schedule; Improve quality of the delivered product; Better Risk Management; Speed-up; Provide more opportunities for customers; Quick responding to changes. Also, Agile is best suited to projects where the problem is complex and may not be fully understood at the beginning of the project. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 7. The main challenges in applying Agile in Waterfall project are to define where exactly in the project to do that and how deep. And Make it timely. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 8. Bad Tetris Your project has to be holistic structure where all processes, tools and resources are at the right place. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 9. Even The most “Agile project” refers to the traditional project management principles and The most ster “Waterfall project” could be Agile Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 10. How to implement Agile? What is Important for Your Project? ● Scope? ● Schedule? ● Budget? If Schedule or Budget: ● You need to set up clear limits on the amount of project budget and project schedule; ● You need to communicate clear and often about all updates and changes. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 11. If Scope: Be clear with management what is in the project backlog versus what is in the product backlog Product Backlog Feature Journey Project Backlog Release Backlog Release Backlog Iteration Backlog Iteration Backlog Iteration Backlog Iteration Backlog Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 12. Do You Need Agile? Criteria to Determine the Best Approach for Your Project ● ● ● ● ● ● ● ● ● ● ● Requirements (how rigid and well defined); Duration (how long is the planned duration); Interfacing systems (numbers & complexity); Project interdependencies (resources overlaps?); Sponsor buy-in (right level of sponsorship); Training for Agile (team/organization; coach availability) Project resources; Team size (how big? can it be broken down to 5-9); Technology/Business domain knowledge; Co-location; Testing Automation. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 13. Where You Need Agile? Product 1 2 3 4 1.1 2.1 3.1 4.1 1.2 2.2 3.2 4.2 1.3 2.3 3.3 1.4 3.4 Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 14. Define what could be done by Agile methodology Product 1 2 3 4 1.1 2.1 3.1 4.1 1.2 2.2 3.2 1.3 2.3 3.3 1.4 Agile 4.2 3.4 Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 15. Define Sprint Backlogs Product 3 4 3.1 4.1 3.1 3.2 3.2 4.2 4.1 4.2 3.3 3.4 3.3 Release 1 Release 2 3.4 Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 16. The Model of The Mixed Project Sprint Backlog Sprint Backlog Start End 1.3 1.1 1.4 1.2 2.3 2.1 2.2 Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 17. The Model of The Mixed Project Sprint Backlog Sprint Backlog ● ● ● ● Start Joint iteration planning Scrum-of-scrum Joint sprint demos Joint retrospectives 1.3 1.1 End 1.4 1.2 2.3 2.1 2.2 Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 18. Agile Project management Techniques User stories VS Requirements Fixed Sprint Duration VS Fixed Scope Self-organizing Team VS PM Lead Team Low-tech communications VS Formal Communications Documents Stand-Up Meetings VS Traditional Project status Meetings Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 19. How to understand that Agile works? 7 Factors for Successfully Adopting Agile 1. Full-time Product Owner 2. Dedicate a full-time Delivery Team 3. Just-in-Time requirement 4. Time-boxing the iterations 5. Having the right people in the right roles 6. A collaborative environment 7. Applying the necessary discipline Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 20. 7 Factors for Successfully Adopting Agile 1. Full-time Product Owner 2. Dedicate a full-time Delivery Team 3. Time-boxing the iterations 5. Having the right people in the right ● Just-in-Time requirement 4. Nokia Test roles ● ● ● ● ● 6. A collaborative environment 7. Applying the necessary discipline ● ● Sprints must be timeboxed to 4 weeks or less; Features are tested and working by the end the Sprint; The Sprint starts with an Agile spec; You know who the product owner is; There is a product backlog prioritized by business value; The product backlog has estimates created by the team; The team generates burndown charts and knows their velocity; There are no project managers (or anyone else) disrupting the work of the team; Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 21. Agile in NASA In 2008 NASA decided to revise the processes for R&D and engineers who are involved in it. For NASA it means to combine traditional approach with creativity, flexibility and adaptivity. ● ● NASA revised requirements for new hiring engineers: ○ proactivity ○ communication skills ○ problem solving skills ○ leadership New training programme to develop necessary skills New rules for engineering teams to develop creativity and open climate: 1. Status means nothing in taking decisions; 2. Certainty is a main argument in taking decisions 3. Autonomy for engineering teams. From outside come just functional requirements, budget and time. 4. Relatedness is important in relationship between team-mates. 5. Fairness is important in judgments and taking decisions. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 22. Lean Project Management Evaluate the flow of work to identify opportunities for improvement: ● Reduce “Non-Value Add” activities and increase “Customer Value Add” activities ● Improve Project by agile techniques Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 23. Failure in Applying Agile Agile, like any other framework or process is not bad, only people who made decision to apply and didn't learned carefully the project environment. ● ● ● ● ● ● ● ● ● The Signed "Waterfall" Contract; Wrong people in the right roles; Cultural clash; Team doesn't support changes; Product owner wasn’t defined or not available; Project environment doesn't support Agile approach; Weak understanding of Agile principles and tools; Unexperienced Project manager and team; and etc. Maksym DOVGOPOLYI, Applying Both Agile & Waterfall in One Project, Geneva, 2013
  • 24. B “Be water, my friend” Bruce Lee Maksym DOVGOPOLYI, Applying both Agile & waterfall in one project, Geneva, 2013