Watch this webinar recording to learn about the fundamentals of Waterfall and Agile development, as well as the “Agifall” Hybrid solution that aims to combine the benefits of both approaches. After introducing both approaches, this webinar discusses the two most widely used Agile methodologies: Scrum and Kanban. Through a live demonstration, the webinar also shows you how to manage projects with either of these development frameworks in codeBeamer.
http://intland.com/webinar/2015-03/development-with-agile-waterfall-and-agile-waterfall-hybrid-2/
Webinar: Development with Agile, Waterfall and Agile-Waterfall Hybrid
1. Agile, Waterfall or Hybrid?
What is the difference and which methodology to use?
Eva Johnson and Sandor Szabo
18 March, 2015
2. 2
Agenda
1. Introduction of Intland Software
2. Waterfall in a nutshell
3. What we know about Agile/Scrum/Kanban
4. When-Why-How to use the Agile-Waterfall Hybrid?
5. The main challenges of the Agile-Waterfall Hybrid model
6. Live demo of codeBeamer ALM
3. 3
o Founded in 1998
o Headquarter in Stuttgart, Germany
o Office in Silicon Valley, USA
o Partners in Korea & Taiwan
o codeBeamer ALM with features including:
• Requirements Management
• Software Development Management
• QA-Test Management
• Demand Management
• IT Operations (DevOps)
Intland Software
Who are we?
5. 5
Agile-Waterfall-Hybrid Software Development
What is Waterfall?
• Waterfall is a popular development model for software engineering.
• It is in use since the 1960’s for large scale projects.
• Long delivery cycle, separate testing phase and requirements with no change.
• Waterfall model describes a development method that is linear and sequential.
• Once a phase of development is completed, the development moves to the next phase.
Requirements
Design
Implementation
Verification
Maintenance
6. 6
Agile-Waterfall-Hybrid Software Development
What is Agile?
• Agile software development is a group of software development methodologies.
• Based on iterative and incremental development.
• Focus on keeping code simple, testing often, and continuous delivering.
• Shorten the delivery time.
• Enable to collect feedback in early stages to fulfill better the requirements.
• It is widely considered the best for quick product development.
• The two most widely used methods are Scrum and Kanban.
8. 8
Agile-Waterfall-Hybrid Software Development
Agile-Waterfall Hybrid in a nutshell
• Marriage of Agile and Waterfall methods.
• The two methods are fundamentally very different.
• Lead to benefits that cannot be achieved by using a single method.
9. 9
Agile-Waterfall-Hybrid Software Development
When-Why-How to use the Agile-Waterfall Hybrid?
• WHY
• Shorten design, analysis and planning, but define project frames
• Be compliance with standards.
• Results more collaboration.
• WHEN
• 1. Product development (hardware / manufacturing / service with software)
• 2. n-tier application development
• HOW
• Planning with Waterfall but development with Agile/Scrum
• Implement new types of communications
• Involve Product Owners and clients
10. 10
Agile-Waterfall-Hybrid Software Development
Challenges of the Hybrid Method
• Cultural differences
• Waterfall teams do more documentation and they are less cooperative
• Agile teams do less documentation and they are more cooperative(daily stand up/retrospective)
• Technical challenges
• The dependency tracking, overseeing complex structures/hierarchies and clarity of Waterfall and Agile
• Merging both approaches in the release(s)