Managing Requirements

in an Agile Development Environment

Mai-Lan Tran

18 November 2015

2

Agenda

1. Introduction of Intland Software

2. Basics of Agile Development

3. Managing Requirements in an Agile

Environment

4. Ensuring traceability throughout the

lifecycle

5. Scrum and Kanban

6. Live demonstration

3

Managing Requirements in an Agile Development Environment

Webinar info

o Live demonstration will be followed by

a Q&A session

o Webinar recording will be available at

www.intland.com/webinars/

o Please register to our upcoming

webinars

o Agile IT Operations: Managing

DevOps Processes

4

o Founded in 1998

o Headquarters in Stuttgart, Germany

o Office in Silicon Valley, CA, USA

o Partners Lufthansa Industry Solutions,

and resellers in Korea & Taiwan

o codeBeamer ALM components:

• Requirements Management

• Software Development Management

• QA & Test Management

• Demand Management

• IT Operations (DevOps)

Intland Software

Introduction

5

Intland Software

Automotive

High Technology

Defense

Finance

Medical

Other

Our Clients

6

What is Requirements Management?

“A systematic approach to eliciting, organizing and documenting the requirements of

the system, and establishing and maintaining agreement between the customer and

the project team on the changing of requirements of the system” (NYU, 2012).

Intland Software

Requirements Management

7

What is Agile?

“Agile is a time boxed, iterative approach to software delivery that builds software

incrementally from the start of the project, instead of trying to deliver it all at once

near the end.” (agilenuteshell.com)

Intland Software

The Agile Maniesto

Individuals and interactions over Processes and tools

Customer collaboration over Contract negotiation

Working software over Comprehensive documentation

Responding to change over Following a plan

“That is, while there is value in the items on the right, we value the items on the left more” (Agile Manifesto)

8

Intland Software

• 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.

Basics of Agile Development

9

• Major Challenges for Requirements Management

• Traceability along various stakeholders and items

• Communication along the process

• Prioritize requirements according to its business value

• Large number of requirements

• Overview of Project Status

• Major Challenges for Agile

• Communication with all stakeholders

• Short release cycles complicate the prioritization of items

• Difficult to enforce traceability

• Adapting to changes within the requirements while working on products

• Coordinate distributed teams

Challenges

Why use a tool?

10

• All goals are traced along the completeness of requirements

• Change management ensures easier impact analysis, and

improved risk management

• Helps to avoid quality and acceptance problems

• Enables further improvement of the product and maintenance

• Save time/money and effort – product fits to business needs

• Reduced waste time due to less failures with a decreased chance

of project overrun

• Ensure compliance with industry standards (CMMI, ISO 900X)

• Provides a quicker impact analysis for risk time and cost

deviations

Intland Software

Ensuring traceability throughout the lifecycle

11

Artifact Traceability

• Artifacts (work items such as

requirements, tasks, test

cases, etc) are referenced to

each other

• provides end-to-end

traceability throughout the

lifecycle

Historical Traceability

• Each and every artifact stores

its own history, letting you

control all changes, and

browse all previous versions

Project Traceability

• highest level of traceability

practically means complete

project transparency

Three dimensions

End-to-End Traceability

12

Intland Software

Scrum

Agile planning, Sprint, Daily

stand up, Retrospective

Lean / Kanban

Task management,

visualisation, WIP (overload)

Scrum and Kanban

13

Live demo

Thank you for your attention!Any questions?

sales@intland.com