Agile, Waterfall or Hybrid?What is the difference and which methodology to use?

Eva Johnson and Sandor Szabo18 March, 2015

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

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 SoftwareWho are we?

4

Our Clients

Automotive

High Technology

Defense

Finance

Medical

Other

5

Agile-Waterfall-Hybrid Software DevelopmentWhat 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

DesignImplementatio

nVerification

Maintenance

6

Agile-Waterfall-Hybrid Software DevelopmentWhat 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.

7

Agile-Waterfall-Hybrid Software DevelopmentScrum vs. Kanban

SCRUMAgile planning, Sprint,

Daily stand up, Retrospective

KanbanDaily task management,

status update, WIP (overload)

8

Agile-Waterfall-Hybrid Software DevelopmentAgile-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

Agile-Waterfall-Hybrid Software DevelopmentWhen-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

Agile-Waterfall-Hybrid Software DevelopmentChallenges 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)

11

Agile-Waterfall-Hybrid Software DevelopmentHybrid in codeBeamer ALM

12

Agile-Waterfall-Hybrid Software DevelopmentcodeBeamer ALM

13

codeBeamer Live Demo

14

Webinar: Kanban or Scrum – Is Scrum for developers and Kanban for IT support?

Date: 25 Mar 2015Time: 4:00 PM (CET) / 10:00 AM (EST)

15

Thank youfor your attention!