Essence--Creating Winning Teams

43
Copyright © 2013 Ivar Jacobson International SA. All rights reserved Essence Ivar Jacobson with Ian Spence and Pan Wei Ng

description

Presentation on Essence (OMG Standard for Software Engineering Kernel and Language) and its applications in industry by Dr. Ivar Jacobson in the SEMAT Korea Conference on Essence in Seoul, Korea on October 18, 2013

Transcript of Essence--Creating Winning Teams

Page 1: Essence--Creating Winning Teams

Copyright © 2013 Ivar Jacobson International SA. All rights reserved

Essence Ivar Jacobson

with Ian Spence and Pan Wei Ng

Page 2: Essence--Creating Winning Teams

Page 2

The SEMAT initiative

Software Engineering Method And Theory Founded in September 2009: Ivar Jacobson – Bertrand Meyer – Richard Soley 40 individual signatories 2,000 supporters – 20 corporate signatories – 20 academic signatories

COMMUNITY www.semat.org

Page 3: Essence--Creating Winning Teams

Page 3

What is SEMAT?

Let’s wait a little by getting into what it is Let’s instead start by saying •  It doesn’t compete with any method – agile or pre-agile •  Instead it powers other methods/practices – agile or pre-agile

Scrum DSDM

Prince Disciplined Agile Delivery

Scaled Agile Framework

Unified Process

User Stories

Use Cases 2.0

Architecture

System of Systems Powered By

Page 4: Essence--Creating Winning Teams

Page 4

There are particularly three things that are new with SEMAT

1.  SEMAT relies on a common ground or a kernel

2.  The kernel is actionable

3.  It relies on an intuitive graphical syntax

Demonstrable

Usable

Ready

Operational

Softw

are

Syst

em

Architecture Selected

Retired

Page 5: Essence--Creating Winning Teams

Page 5

There are particularly three things that are new with SEMAT

1.  SEMAT relies on a common ground or a kernel

2.  The kernel is actionable

3.  It relies on an intuitive graphical syntax

Demonstrable

Usable

Ready

Operational

Softw

are

Syst

em

Architecture Selected

Retired

Page 6: Essence--Creating Winning Teams

Page 6

A Specific Problem: We have no Common Ground

We don’t lack methods or practices Everyone of us knows how to develop our own software, but as a community we have no widely accepted common ground

Six Sigma

PRINCE2

Waterfall

Use Cases

SAFe

Kanban

User Stories

Pair Programming CMMI ATDD

Spiral

Page 7: Essence--Creating Winning Teams

Page 7

SEMAT advocates a Common Ground/a Kernel

SEMAT provides a common ground/a kernel on top of which more specialised practices/methods can stand

Common Ground – The Kernel

Copyright © 2013 Ivar Jacobson International SA. All rights reserved

Scrum Use Cases

User Stories

Pair Programming CMMI ATDD

Page 8: Essence--Creating Winning Teams

Page 8

SEMAT started to find a Common Ground – a Kernel

•  At the heart of the the SEMAT approach is the Kernel •  A simple state-driven model of software development •  Things that are universal to all software development endeavors.

Page 9: Essence--Creating Winning Teams

Page 9

On top of the Kernel …

•  Practices can be added to create your specific Way of Working. •  Practices such as Scrum, User Stories, Test-Driven Development, etc. •  But that is not the subject of today.

Practices

Page 10: Essence--Creating Winning Teams

Page 10

The Kernel and its Alphas

Opportunity Stakeholder

Team

Way of Working

Work

supports

identifies

performs and plans

produces

Updates and changes

fulfills

uses and consum

es

focuses

scopes and constrains

set u

p to

add

ress

Cus

tom

er

Sol

utio

n E

ndea

vor

Requirements Software System

Page 11: Essence--Creating Winning Teams

Page 11

There are particularly three things that are new with SEMAT

1.  SEMAT relies on a common ground or a kernel

2.  The kernel is actionable

3.  It relies on an intuitive graphical syntax

Demonstrable

Usable

Ready

Operational

Softw

are

Syst

em

Architecture Selected

Retired

Page 12: Essence--Creating Winning Teams

Page 12

The Kernel is more than a static model – it is actionable

Opportunity

Requirements

Stakeholder

Software System

Team

Way of Working

Work

supports

identifies

performs and plans

produces

Updates and changes

fulfills

uses and consum

es

focuses

scopes and constrains

set u

p to

add

ress

Cus

tom

er

Sol

utio

n E

ndea

vor

Page 13: Essence--Creating Winning Teams

Page 13

The alphas have states and checklists

Opportunity

Requirements

Stakeholder

Team

Way of Working

Work

supports

identifies

performs and plans

produces

Updates and changes

fulfills

uses and consum

es

focuses

scopes and constrains

set u

p to

add

ress

Cus

tom

er

Sol

utio

n E

ndea

vor

Software System

Demonstrable

Usable

Ready

Operational

Softw

are

Syst

em

demonstrates quality characteristics required

accepted for operational deployment

in use in an operational environment

Architecture Selected

Retired

addresses the key technical risks and any constraints

proves architecture, concept and supports testing

no longer supported

Page 14: Essence--Creating Winning Teams

Page 14

Software Development is a multi-dimensional Endeavor

Every Alpha represents one dimension

http://sematacc.meteor.com/

Page 15: Essence--Creating Winning Teams

Page 15

There are particularly three things that are new with SEMAT

1.  SEMAT relies on a common ground or a kernel

2.  The kernel is actionable

3.  It relies on an intuitive graphical syntax

Demonstrable

Usable

Ready

Operational

Softw

are

Syst

em

Architecture Selected

Retired

Page 16: Essence--Creating Winning Teams

Page 16

Essence made tangible with well-formed graphics

c a r d s & c h e c k l i s t s

Page 17: Essence--Creating Winning Teams

Page 17

Play the Games

•  You can play many games

•  http://www.ivarjacobson.com/alphastatecards/

Progress Poker Lifecycle Layout

Chase the State Milestone Mapping

Objective Go Health Monitoring

Checkpoint Construction

And more……

Page 18: Essence--Creating Winning Teams

Page 18

Plan: Determine Current State

All Alpha States Lined Up App soon to be

available

Page 19: Essence--Creating Winning Teams

Page 19

Plan: Determine Current State

All Alpha States Lined Up

Page 20: Essence--Creating Winning Teams

Page 20

Checkpoints for an example state

Page 21: Essence--Creating Winning Teams

Page 21

Plan: Determine Current State

Achieved States

Pending States

Page 22: Essence--Creating Winning Teams

Page 22

Plan: Determine Next State

Achieved States

Pending States

Next States to Achieve

Page 23: Essence--Creating Winning Teams

Page 23

Plan: Determine How to Achieve Next State

Next States to Achieve

Page 24: Essence--Creating Winning Teams

Page 24

Plan: Determine How to Achieve Next State

Next States to Achieve

Page 25: Essence--Creating Winning Teams

Page 25

Plan: Determine How to Achieve Next State

Next States to Achieve

Page 26: Essence--Creating Winning Teams

Page 26

Plan: Determine How to Achieve Next State

Next States to Achieve

Page 27: Essence--Creating Winning Teams

Page 27

Applying the Essence

Helping Agile Teams

And Agile Organizations

Page 28: Essence--Creating Winning Teams

Page 28

Applying the Essence

Helping Agile Teams

And Agile Organizations

Page 29: Essence--Creating Winning Teams

Page 29

Taking a holistic approach and exploiting the common ground

All 7 CMU-SV practicum teams used different sets of s/w engineering practices

Progress & Health

•  Measure progress & health of your teams regardless of practices selected.

Avoiding Problems

•  Detect systemic problems early & take appropriate action

Reprinted by permission of Cecile Peraire, CMU West

Page 30: Essence--Creating Winning Teams

Page 30

Getting Started

Understanding where you are •  What’s already been

achieved? •  What are the risks? In Action: •  An internal coach in a

large telecom product company.

Benefits: •  Detected risks in

working with stakeholders.

Page 31: Essence--Creating Winning Teams

Page 31

Scaling Up

Scaling Up •  How to help large

development team collaborate

In Action: •  Large development

involving offshore members (50+200) developers

Benefits: •  Cards facilitate

describing new way of working

•  Cards help new (feature) team leaders guide members 8

Core Patterns & Practices

10+20 OffShore Induction

Learn, Demo

30+100 Even More

Feature Team

20+50 More Feature

Team

Page 32: Essence--Creating Winning Teams

Page 32

The Kernel provides a shared frame of reference

The Kernel

Many Ways of Working on the same kernel.

Offshore Product Development Lean Offshore

Architecture Use Case

Internet Development

Scrum

User Story

Acceptance Test Driven

Lean

Scrum

Consumer Product Development

Use Case

Page 33: Essence--Creating Winning Teams

Page 33

SEMAT for Agile Teams - Summary

•  Understand where you area and where you are going –  Understand what needs to be addressed –  Holistically track progress and health –  Keep projects in balance and avoid catastrophic

failures –  Form good sprint goals and other objectives –  Bring people together

•  Learn and share your way of development –  Share and compare practices –  Build effective ways of working –  Define practice independent checkpoints, and

lifecycles

The Value of Essence

Page 34: Essence--Creating Winning Teams

Page 34

Applying the Essence

Helping Agile Teams

And Agile Organizations

Page 35: Essence--Creating Winning Teams

Page 35

There are several case studies

•  KPN, a large telecom operator relying on outsourcing •  Fujitsu UK •  Munich Re, a large insurance company working all around the

world

Page 36: Essence--Creating Winning Teams

Page 36

Munich Re: A common model and an individual way-of-working

The challenge

•  Globally distributed Application Dev’t

•  High-levels of out-sourcing & off-shoring

•  Service organization

The solution

•  Agile starter packs

•  Practice Exchange

•  Governance as a first class citizen

Page 37: Essence--Creating Winning Teams

Page 37

MunichRe: A common procedural model and an individual way-of-working

The challenge

•  Globally distributed Application Dev’t

•  High-levels of out-sourcing & off-shoring

•  Service organization

The solution

•  Agile starter packs

•  Practice Exchange

•  Governance as a first class citizen

Page 38: Essence--Creating Winning Teams

Page 38

SEMAT for Agile Organizations - Summary

•  Define practice independent governance procedures and quality gates.

•  More readily and easily form teams and mobilize teams of teams. •  Scale agile approaches across teams of teams and systems of

systems. •  Select enterprise level tooling.

Page 39: Essence--Creating Winning Teams

Page 39

In a Nut Shell – what SEMAT will change

Executives Big companies have many methods. Challenges: - Reuse practices - Reuse training - “Reuse” of people - Evolutionary improvement is hard

Professionals Want to become experts. Challenges: - Their skills are not easily reusable for a new product. - Their career path follows a zig-zag track from hype to hype.

Education - Teaching instances of methods such as Scrum, RUP, instead of common base; doesn’t create generalists

SEMAT targets the whole software community.

Industry Academics Research - The Gap between research and industry - No widely accepted theory

Page 40: Essence--Creating Winning Teams

Page 40

Conclusion: SEMAT and Agile Perfect Partners

Page 41: Essence--Creating Winning Teams

Page 41

Get the cards and play the games

http://www.ivarjacobson.com/alphastatecards/

•  Join the community and get involved •  Become a supporter.

Go to www.semat.org •  Or read the book

c a r d s & c h e c k l i s t s

g m a e s

Page 42: Essence--Creating Winning Teams

Page 42

www.ivarjacobson.com

Page 43: Essence--Creating Winning Teams

Page 43

Questions

•  Email - [email protected]

•  OMG website - www.omg.org

•  SEMAT website - www.semat.org