You are on page 1of 1

Mode 1

The Agile Software Development Lifecycle


Implementation

SignOff

Test

1
Sprints

2 Define

3 Sprints

Strategy & Vision

Preparation (Sprint 0)
Product Backlog
Decomposition

Budget
Definition

Systems & Technologies


Are Software/Technologies suitable for agile development?

Team
Definition

Roles
Product
Owner

PO

Project, Process & Organization

Development Duties &


Responsibilities
Team
Estimation of user
overall

Application
Deployment

SM

Duties &
Responsibilities
Supports the team and
helps them to develop
and reach its goals
Keeps Scrum artifacts
visible

Duties &
Responsibilities
Compilation of test
Define test approach/
protocols
create test cases/
Identification of
Compilation of
regression test set
release notes
Execute acceptance tests Test execution of
RIT test
Create test reports
Test execution of
Planning/execution of
UAT & OAT test
integration tests
Refine application design
Handle defects
Build management/
configuration
management
Create test data
Documentation

In each phase of the


development lifecycle
deliverables are defined
Pr
ep
that are either regulatory
ar
at
or best practices
io
n
Stakeholder
Deliverables help
List
making project progress
List of Epics
measurable
Vision
Budget Approval
Some deliverables have
Strategy & Vis
ion
to be considered because
of regulatory aspects
Templates/tools are
SW Deployment
Package
defined for all deliverables
y
plo
De

HL Arch.
Product
Backlog

Build & Deploy.


Fact Sheet

DoR

IT Security
Concept

(Master)
Test Plan

Agile Core
Process Model
Si
g
Off n-

Business/
Operation
Sign-Off

Release
Plan

DoD

fine
De

Test Status
Report

Release
Plan

Product
Backlog

(Master)
Test Plan

Test
Sprints
Test End
Report

Project
Closure
Summary of learnings
and adaptions
Perform project closure
procedures

Product Management
PO

Product
Backlog

Test Status
Report
(Integration)
Test Protocol

(Master)
Test Plan

Test Status
Report

Application
Documentation

Design
Specification

SW
Increments

Development and Operation


Software hand-over happens in small increments
Team members from production participate in
Scrum meetings and keep production up to date
Production team members are informed right
from the beginning about release scope and
milestones
Members of the Scrum team may take
responsibility for production tasks
Production team members may actively support
the preparation of the increment (segregation of
duty rules to be considered)

Dirk Jaensch
Partner
dirk.jaensch@bearingpoint.com
2016 BearingPoint GmbH

PO

SM

DT

SM

DT

SM

DT

DT

DT

DT

DT

DT

DT

DT

DT

DT

DT

DT

DT

Scrum team 2

Architecture
Resource Management
Deployment

Development & Operation


Team
DT

DT

DT

DT
DT

Scrum team n

Release Management

DT

Contacts

Impediment
Backlog
Test Cases

Burn Down
Chart
Release
Plan

Product
Backlog
Software
Product
Deployment
Instructions

Sprint
Backlog
Scrum
Board

Status
Report

PO

Scrum team 1

Deliverables

Release
Notes

Shields the team from


external interference
Helps to remove
impediments

7 Closure

Deployment of the
application and hand
over to production

The sprint phase represents the heart of the model. Work according to the Scrum methodology, including Scrum
artefacts and meetings. The team should not be interrupted while they are in a sprint phase. The increment
implementation as well as the integration represent all activities that have to be done while sprinting.

Sprint
s

Is business willing to spend as much time as necessary?

Duties &
Responsibilities
Define workspace and
collaboration model
Define Scrum process
details
Create DoR and DoD

Governance activities
Sprint planning & sprint
review
Involve production

Duties &
Responsibilities
Product Sign-Off
Support of integration
planning
Part of retrospective
Documentation of
lessons learned

6 Deploy

Application
Documentation
Maintenance

Test
Preparation

Scrum
Master

Application Governance Activities


Test
Execution

D e pl o

Do we have a clear picture about the outcome of the


project?
Is the developed product bound to rapidly changing
standards?

Increment
Implementation

Test Sprint

Closure
Activities

Application
Deployment

Management of
a flawless sign-off

Development Team and Program Management


Multiple Scrum teams work together
Consideration of special functions
(e.g. chief product owner that has overall
project responsibility)
Special interest groups represent communication
across the teams
(communities of practice)
Cross functional entities support the
development teams

Production
Preparation

Code
Development

Deploy

Organization

ion
grat
Inte

Clarity & Focus

Duties &
Responsibilities
Support in backlog
refinement
stories
Estimation of user stories
Define & setup
development & test
Perform sprint planning
infrastructure
Perform daily Scrum
Define & setup of
Create code
development tools
Design and automate
Support in Epic
tests
creation &
Execute (automated)
decomposition
tests
Support in creation of Help to discover users
DoR and DoD
needs

Environment
Setup

SignOff

Acceptance
Management

Production
Transition

uct
Prod
Live ort
p
Sup

DT

Readiness of Business

Duties &
Responsibilities
Continuous backlog
refinement support
for test planning
User story acceptance
Update release plan

Validation of the
integration on release
level

Daily
Scrum

Application Build
Management

Sprints

Sprint
Review

5 Sign-Off

Test
Execution

ent
rem tion
Inc enta
lem
Imp
ning nt
Planageme
an
&M

Is there a benefit to get early feedback and involve


stakeholders throughout the project?
Will the product be implemented in a one-time
implementation or in a continuous evolution?

Duties &
Responsibilities
Creation of product
vision
Prototyping
High level backlog
management
Budgeting
Team setup
Release planning
Governance activities

Planning &
Management
(Scrum)

Integration
Planning

Create the project vision and roadmap and define the team. The team gets ready for the first sprint. Specification of the overall scope (releases) including product backlog decomposition, System Architecture and release
planning. Setup of the process details as well as the infrastructure.

Define

Backlog
Refinement

Integration

Define Process
Details

Do we have a contract type that supports agile


development?

Do we have an experienced cross-functional team?


Is the whole team located in one place / are there
sufficient collaboration tools?

Integration
Testing

4 Test
Sprint

Sprint
Retrospective

Prepare Project
Infrastructure

Does Senior Management support working in an agile


environment?

People & Workspace

Test Sprint

Sprint
Planning

HL System
Architecture

Product
Ideation

Management

Release
Planning

Jrg Steinbauer
Partner
joerg.steinbauer@infonova.com

Cross Team
Functions

Define

Mode 2

Readiness of Partner

Development
Teams

Mode 1

Closure
Activities

Deploy

Program
Management/
Governance

The project Applicability Matrix helps you to choose the


right operating and process model.

print
Test S

Mode Decision

Acc
epta
nce

Design

Scaled model with several applications & projects to consider:


Joint post development test phase and coordinated deployment

Mode 2

Project
Start

Requirement Analysis