Practices and Methods: Realizing the SEMAT Vision

Creating winning teams.

www.ivarjacobson.com

Practices and Methods: Realizing the SEMAT Vision

Ian Spence


The Future: Practice Independence

A Declaration of Practice Independence

We hold these truths to be self-‐evident, that all prac6ces are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are life (constant evolu6on), liberty (method independence) and

the pursuit of excellence.


The Future: No More Method Wars


The Future: Better Software Development


The Future: Better Teams


The Future: It’s Here Today


Welcome to the World of Practices

Introducing the IJI Essen6als


Capturing the essence of your way-of-working

A Sat-‐Nav for your projects.

Know where you are and where you are going.

Check progress and health.

Collect evidence in a lightweight fashion

Bringing people together to create winning teams, create one culture, and increase staff mobility

The Essence Kernel is a small prac6ce independent process that captures the common ground that is the basis for all your work.

A Method Founda-on

Capture your prac6ces and dynamically assemble your

ways-‐of-‐working.


To realize the vision we need practices

Generic Prac-ces Standard prac6ces to support effec6ve team working and sound engineering principles.

Domain Specific Prac-ces Extensions to the generic prac6ces and addi6onal domain specific prac6ces

The Common Ground The basic concepts applicable to all

captured as a Kernel

Tac-cs and tricks Local team prac6ces captured as a set of

Working Prac6ces


Introducing IJI Essentials

2015.01

©"

Agile&Esse

n*als&Pra

c*ces&

Product

Ownersh

ip

Essential

s

Product

Backlog

Essential

s

Agile

Teaming

Essential

s

Agile

Developm

ent

Essential

sAgile

;

Timeboxin

g

Essential

s

Daily

Stand@Up

Essential

s

Agile

Retrospe

ctive

Essential

s

Iterative

Component

Architecture Use Case

Modeling Process Team

EssUP Practices

Product

$

Agile&at&Scale&

Product&Management&

Release&Management&

Team6of6Teams&

Development&Support&

Periodic&Alignment&

DevOps&

Agile&Architecture&

Adap=ve&Funding& Agile&Governance& Shared&Backlog&



2015.01

©"

Agile&Esse

n*als&Pra

c*ces&

Product

Ownersh

ip

Essential

s

Product

Backlog

Essential

s

Agile

Teaming

Essential

s

Agile

Developm

ent

Essential

sAgile

;

Timeboxin

g

Essential

s

Daily

Stand@Up

Essential

s

Agile

Retrospe

ctive

Essential

s

Iterative

Component



EssUP Practices

Product

$

Agile&at&Scale&

Product&Management&

Release&Management&

Team6of6Teams&


Periodic&Alignment&

DevOps&

Agile&Architecture&


2015.01 ©"

Use$Case$2.0$A"scalable,"agile"prac.ce"that"uses"use"cases"to"capture"a"set"of"requirements"and"drive"the"incremental"development"

of"a"system"to"fulfil"them."

Find%Actors%&%Use%Cases!

Slice%the%%Use%Cases!

Prepare%a%%Use6Case%Slice!

!Test%%Case!

Inspect%&%Adapt%the%Use%Cases!

Planning%Poker%%with%Story%Points%

Use%Case! Use6Case%Slice!

Use6Case%Model!

Use6Case%Narra?ve!

Suppor?ng%Informa?on!

Use6Case%Realiza?on!

Analyze%a%%Use6Case%Slice!

2015.01 ©"

User%Story%%Essen,als%Capture(what(the(users(of(a(so.ware(system(want(it(to(do(in(an(informal(way(as(part(of(an(agile(way(of(working.(

.(

US"

described(by!!

User%Story!

Story%Card!As%a%…%I%Want%%…%So%That%…%

Find%User%Stories!

Three%C’s%

Split%a%%User%Story!

Prepare%a%User%Story!

!Test%Case!

Accept%a%%User%Story!

Planning%Poker%with%Story%Points%

Product%Owner%

Scrum&Esse

n+als&

A"framewor

k"within"wh

ich"people"c

an"address

"complex"

adap5ve"p

roblems,"w

hile"produc

5vely"and"

crea5vely"

delivering"p

roducts"of"

the"highes

t"possible"

value."

Sprint''

Planning'

Scrum''

Team'

Sprint'

Sprint'Goa

l'Sprin

t''

Backlog'

Improvement'

Impediment'

Daily''

Scrum'

Sprint''

Review'

Sprint'

Retrospec=

ve'

Developm

ent'

Team'

Product'

Owner'

Scrum'Master

'

Product''

Backlog'Ite

m'Incre

ment'Defin

i=on'of'

Done'

Product''

Backlog'

Scrum&



2015.01

©"

Agile&Esse

n*als&Pra

c*ces&

Product

Ownersh

ip

Essential

s

Product

Backlog

Essential

s

Agile

Teaming

Essential

s

Agile

Developm

ent

Essential

sAgile

;

Timeboxin

g

Essential

s

Daily

Stand@Up

Essential

s

Agile

Retrospe

ctive

Essential

s

Iterative

Component



EssUP Practices

Product

$

Agile&at&Scale&

Product&Management&

Release&Management&

Team6of6Teams&


Periodic&Alignment&

DevOps&

Agile&Architecture&


2015.01 ©"

Use$Case$2.0$A"scalable,"agile"prac.ce"that"uses"use"cases"to"capture"a"set"of"requirements"and"drive"the"incremental"development"

of"a"system"to"fulfil"them."

Find%Actors%&%Use%Cases!

Slice%the%%Use%Cases!

Prepare%a%%Use6Case%Slice!

!Test%%Case!

Inspect%&%Adapt%the%Use%Cases!

Planning%Poker%%with%Story%Points%

Use%Case! Use6Case%Slice!

Use6Case%Model!

Use6Case%Narra?ve!

Suppor?ng%Informa?on!

Use6Case%Realiza?on!

Analyze%a%%Use6Case%Slice!

2015.01 ©"

User%Story%%Essen,als%Capture(what(the(users(of(a(so.ware(system(want(it(to(do(in(an(informal(way(as(part(of(an(agile(way(of(working.(

.(

US"

described(by!!

User%Story!

Story%Card!As%a%…%I%Want%%…%So%That%…%

Find%User%Stories!

Three%C’s%

Split%a%%User%Story!

Prepare%a%User%Story!

!Test%Case!

Accept%a%%User%Story!

Planning%Poker%with%Story%Points%

Product%Owner%

Scrum&Esse

n+als&

A"framewor

k"within"wh

ich"people"c

an"address

"complex"

adap5ve"p

roblems,"w

hile"produc

5vely"and"

crea5vely"

delivering"p

roducts"of"

the"highes

t"possible"

value."

Sprint''

Planning'

Scrum''

Team'

Sprint'

Sprint'Goa

l'Sprin

t''

Backlog'

Improvement'

Impediment'

Daily''

Scrum'

Sprint''

Review'

Sprint'

Retrospec=

ve'

Developm

ent'

Team'

Product'

Owner'

Scrum'Master

'

Product''

Backlog'Ite

m'Incre

ment'Defin

i=on'of'

Done'

Product''

Backlog'

Scrum&

2015.01

©"

Use$Case$

Goal"Establis

hed"

Sufficient"Stories

"Fulfilled"

All"Stories"Fu

lfilled"

All#the#ways#

of#using#a##

system#to#ach

ieve#a##

par6cular#g

oal#for#a##

par6cular#u

ser.#

Requirements"

Relates"to:"

Story"Under

stood"

Simplest"Story"F

ulfilled" 2015.01 ©"

Use$Case''Narra*ve'

The$purpose$of$a$use,case$narra/ve$is$to$tell$the$story$of$how$the$system$and$its$actors$work$together$to$achieve$a$par/cular$goal.$$

Bulleted"Outline"

Essen.al"Outline"

Fully"Described"

Use"Case"Describes:"

Briefly"Described"

2015.01 ©"

Find%Actors%and%Use%Cases%

Agree%on%the%goals%and%value%of%the%

system%by%iden5fying%ways%of%using%

and%tes5ng%it.%

3"Analysis"

2"Stakeholder"Rep."

Understand"the"Requirements"

User"Case:"Goal"Established"

Use@Case"NarraBve:"Briefly"Described""

Requirements:"Shared"

Use@Case"Model:"Value"Established"

SupporBng"informaBon:"IniBated"

2015.01 ©"

Use$Case'Slice'

Scoped"

Implemented"

Verified"

One$or$more$stories$$selected$from$a$use$case$$to$form$a$work$item$that$is$of$clear$value$to$the$customer.$$

Use"Case"Relates"to:"

Prepared"

Analyzed"


Available Electronically



The raw prac6ce. Also directly accessible from the prac6ce

overview page.

The raw prac6ce. Also directly accessible from the prac6ce overview page.

The prac6ce in the context of the kernel, which is as it would appear when composed in a method.

Direct access to suppor6ng resources such as the cards, examples, references and templates

All generated from Prac6ce Workbench for individual prac6ces and methods composed from sets of prac6ces.



Uses the language to demonstrate the rela6onship between elements and aid

naviga6on.

All the informa6on about an element on one simple,

scrollable page.



Checklist presented in an easily accessible and printable format.



Addi6onal embedded guidance can be provided as part of the prac6ce but is not obligatory.


Define combina-ons that occur frequently

Iterative Essentials

Architecture Essentials

Use-Case Essentials

Team Essentials

Component Essentials

Scrum Essentials

User Story Essentials

Product Development

Essentials

Unified Process

IJI Essentials: Liberating the Practices

Individual teams can add addi-onal

prac-ces to their Way of Working


Mix and Match Practices to Empower Your Teams

Team A

Team B

Team C

Use Case

Component

Architecture

Itera6ve

Component

User Story Scrum

up

Agile Development

Use Case Con6nuous

Flow Team’s build their way-of-working on top of pre-defined common ground and in-line with organizational principles and policies.

Prac6ces enable teams to work the way that works for them


Example: Rule Financial

Project: rulebook™ -‐ Defined

assembled in

to

Project: rulebook™ -‐ Exploratory

assembled into

Agile Building Blocks

Prac6ces @ Rule Financial


Example: MunichRe

22

Defines how to establish an appropriate architecture and to ac6vely address the technical risks

Defines all quality gates and phases for a project and aligns work products and their quality along the SDLC

Defines how to capture requirements and drive the development

Defines how to set up a team

MR Unified Process

Use Case Essen-als

Component Essen-als

Architecture Essen-als

MR Funding

Itera-ve Essen-als

MR PM for Itera-ve Projects

MR Team Core

Defines the way of managing projects with itera6vely aligned with PMBOK® Guide prac6ces

Release Management

Change Request & Defect

Defines how to acquire from funding process BITA from an IT perspec6ve

Defines how to plan and run itera6ons in a project

Defines how to plan and manage releases in a Product Life Cycle

Defines how to manage change request and defects in a Product Life Cycle.

Defines how to develop complex systems as assemblies of smaller and simpler components

MR Test Management

Defines how to structure and manage for complex and/or risky projects. Based on ITSQB.


New title


New title

It’s a world of prac6ces – and it’s not standing s6ll.


New title

The Kernel the great enabler.



New title

Prac6ces the great communicator.



It’s A Competitive World

IJI Essentials Helping you keep pace

with your technology and your business.


UK Office

+44 (0)1189 001 460 info-‐[email protected]

Asia Office

+8610 824 86030 info-‐[email protected]

www.ivarjacobson.com

Swedish Office +46 8 515 10 174 info-‐[email protected]

North America Office +1 703 338 5421 info-‐[email protected]

Practices and Methods: Realizing the SEMAT Vision

Documents

Transcript of Practices and Methods: Realizing the SEMAT Vision