SPA Conference session: Agile Modelling Practices on Innovative Projects

One-line description:Case study on the role of modeling on agile new development projects providing lessons learned and recommendations
 
Session format: Case study (75 mins) [read about the different session types]
 
Abstract:Agile software development aims to maximize value-creation by reducing any wasteful and non-value creating activities. Upfront analysis, design and modelling activities are hence minimized as much as possible. Modelling plays nevertheless a central role on agile projects, particularly on new product development projects.

How much upfront architecture modelling is required on an agile project? How does the creation of an architecture model influence the team’s estimations and the release plan? And what approaches exist to systematically implement an architecture using test-first whilst at the same time, providing business value?

This talk discusses the delicate balancing act between upfront modelling work and writing code as soon as possible on agile projects using the creation of two new software development projects – one from the enterprise and one from the embedded space – as case studies.
 
Audience background:Basic understanding of agile planning, design patterns, modelling, test-driven development are desired.

Target audience: Project managers/ScrumMasters, product owners, developers and architects
 
Benefits of participating:Improved understanding of the role of modeling on agile projects, useful practices and techniques; understanding of the role of experimentation on agile projects and dedicated experimentation phases; improved understanding on how to balance value creation (shippable product increments) and experimentation
 
Materials provided:PowerPoint slides; additionally, flip charts, whiteboard, projector are required
 
Process:Interactive presentation with about 2/3 of time spent presenting and at least 1/3 spent in discussion allowing the participants to interact with each and engage with the subject
 
Detailed timetable:
 
Outputs:Slides, flipchart paper documenting the results of the discussion parts
 
History:Related work: “Using patterns to create a service-oriented component middleware”, Jim Siddle, Viking PloP 2006. "Experiementieren statt Spekulieren: Architekturmodellierung und Spikes in agilen Projekten“, Roman Pichler and Jim Siddle, to be published in ObjektSPEKTRUM 6. http://www.romanpichler.com/publications/pdfs/pichler_siddle_OS_06_06.pdf
 
Presenters
1. Roman Pichler
Pichler Consulting Ltd
2. 3.