Agile as well as of Lean Thinking is about eliminating waste and focusing on what brings values to your project. Agile requirements definition and management (RDM) is not new but it is a challenge to many companies to fit traditional requirements cycles into the Agile framework. Many companies have hundreds of pages long requirements specifications that is extremely difficult to follow and manage. If you start working with Agile requirements definition and management (RDM) you can start using the same principles for it as used in Agile software development. The aim of our webinar “Agile Requirements Management” was to bring some of the Agile practices to the more “traditional” approach of requirements management. It is important to understand what requirements management is. According to the formal definition of the New York University requirements management is “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”. Principally requirements are differentiated by functional and non-functional requirements such as stability or reliability. Now, we can move to Agile. 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. However, the Agile approach is applied more and more to the development of products. Using Agile approach you can break down your projects into little bits of user functionality called user stories, prioritize them, and then continuously deliver them in short two week cycles called iterations. User stories are features your customers would love to see in their software one day. Watch the webinar's video to see how we focus on Scrum and Kanban and how we can boost you requirements management using Scrum, Kanban and codeBeamer.

1. Agile Requirements
Management
Malte Ackermann 30.10.14
4pm CET

2. 2
Agenda
1. Intland Software
2. Agile Requirements Management
• Requirements Management
• Agile
• Scrum - Kanban
3. Live Demo

3. 3
o Founded in 1998
o Headquarter in Stuttgart
o Office in Silicon Valley
o Partners in Korea & Taiwan
o Sole developer/vendor of codeBeamer
o Consulting and Services from Germany
o Mission ➔ Managing complexity
In the south of Germany and in
the world!

4. 4
Our Clients
o Automotive
Daimler / Ferrari / Continental / s1nn /
MSG Systems / ...
o High Technology
Nintendo / Festo / Fujitsu / Lufthansa
Systems / Sun Oracle / Samsung / ...
o Defense
US Army / EADS / US Navy / RT Logic / ...
o Finance
J. P. Morgan / Allianz / DG HYP /
EasyCash / ...
o Institutional
Bundeskriminalamt / USDA / Fraunhofer / ...
o Medical
Siemens / Thermo Fisher / Jenoptik /
Heine / Bayer / ...
Intland Software

5. 5
•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).
In other words: Guide through the product lifecycle
•Major Challenges:
•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
Requirements Management
Insights

6. 6
•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)
•Major Challenges:
•Various stakeholders -> conflicting interests
•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
•Access for distributed teams
Agile
Insights

7. 7
ScrumKanban
Differences between Scrum and Kanban
Pre-defined roles
No prescribed roles
Short timeboxes(2-4 weeks)
Continuous delivery
Work is pulled by sprints
Work is pulled by system on single item
Velocity
Cycle time

8. 8
Live Demo
Agile Requirements Management
Click heretowatchthevideoofthewebinar!