Essence SW

Development of Essence-based SW Method Composer

/ ( jyjang@uengine.org)
www.semat.org

CONTENTS
Essence

1. IJIs EssWork 2. EssWork Our Approach: Essence

1. Process Orchestration Approach 2. UI Prototyping: Practice Execution 3. Contribution & Differentiator 4. Roadmap

Need for Essence Tool

1. Capitalization (of Practices and Methodologies) 2. Traceability (of Method Execution)

3. Project Performance
4. Project-specific Process Composition

Vision: New Challenge in ALM SW

ALM V

() , /

V V V V V

V V V V V

New challenging SW Tool Market by Essence

Eclipse EPF IBM Rational Method Composer

ScrumWorks

IBM Jazz MS Visual Team Foundation Server

CONTENTS
Essence

1. IJIs EssWork 2. EssWork Our Approach: Essence

1. Process Orchestration Approach 2. UI Prototyping: Practice Execution 3. Contribution & Differentiator 4. Roadmap

 EssWork Practice Workbench

EssWork 1. Interactive presentation of the Essence Kernel 2. Practice authoring and extension using the Essence Language 3. Method composition 4. Innovative card-based representation 5. Publication of methods, practices and kernels as card-based HTMLweb-sites 6. Export to the EssWork deployment environment
6

Visit http://semat.org to find more about EssWork.

Extending the Kernel with Practices to Create Methods Brian Elves ter
SINTEF, Oslo, Norway

www.semat.org

Outline

Scrum Practice Reference Example

Defining the Scrum Practice

Authoring the Practice in the EssWork Practice Workbench Questions

About Scrum
Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules. Scrums roles, artifacts, events, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum. Source
K. Schwaber and J. Sutherland, "The Scrum Guide", Scrum.org, October 2011. http://www.scrum.org/stor age/scrumguides/Scrum_ Guide.pdf

Scrum Concepts

Scrum team (roles)

Product Owner Development Team (of developers) Scrum Master

Scrum events
The Sprint Sprint Planning Meeting Daily Scrum Sprint Review Sprint Retrospective

Scrum artifacts
Product Backlog Sprint Backlog Increment

10

Outline

Scrum Practice Reference Example

Defining the Scrum Practice

Authoring the Practice in the EssWork Practice Workbench Questions

11

Step 0: SEMAT Kernel & Essence Language Concepts

A standard Kernel provides a baseline starting point a "map" of the software development endeavour.
Practices add details and provide specific guidance on particular aspects of the software development Key language concepts: Alpha, Activity Space, Work Product and Activity

Kernel

Practice

Alpha

Work Product

Activity Space

Activity
12

Step 1a: Identify relevant Kernel Alphas

13

Step 1b: Outline the Scrum Practice

Scrum

Requirements

Work

Team

Software System
14

Step 2a: Add sub-alphas

Extending the Work Alpha The Work alpha is typically used for the duration of a development project that may cover a number of sprints. Thus we define a new sub-alpha called Sprint.
Sub-alphas drive their parent alphas

Drives

15

Step 2b: Define alpha states and checkpoints

Specific Scrum rules are defined as part of the alpha state checkpoints.

16

Step 3: Add Work Products

"The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product."
"The Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal." "The Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints."
17

Step 4a: Define Activities

"The work to be performed in the Sprint is planned at the Sprint Planning Meeting." "The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours." "A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed." "The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning Meeting."

18

Step 4b: Identify relevant Kernel Activity Spaces

19

Step 4c: Relate activities to Kernel Activity Spaces

NB! Just one possible suggestion. The organization depends amongst others on how one interpret and define the completion criteria of the Activities.
20

Outline

Scrum Practice Reference Example

Defining the Scrum Practice

Authoring the Practice in the EssWork Practice Workbench Questions

21

Practice Explorer
The Practice Explorer shows Practice Workbench projects The Essence Kernel project contains the elements defined in the OMG Essence specification

Alphas that represent the essential things to work with

Activity Spaces that represent the essential things to do

22

ETextile, Guideline and Card views

The ETextile Source view provides the main editor for authoring the practice using plain text and annotations The Guideline Preview renders how the guideline will be presented in HTML

When selecting an element in the Practice Explorer you can switch between different views

The Overview Card Preview renders the card presentation

23

Scrum Essentials
The Scrum practice is created as a separate practice project in the Practice Workbench

The Scrum practice extends the Essence Kernel by providing more detailed guidance.

Drag and drop the relevant Alphas to extend from the Essence Kernel into the Scrum practice project

Drag and drop the relevant Activity Spaces to extend from the Essence Kernel into the Scrum practice project

24

Scrum Roles
Product Owner (Guideline Preview)

Scrum roles are represented as Patterns

Product Owner (Card Preview)

25

Scrum Sprint

Sprint (Card Preview)

Sprint is represented as a sub-alpha of Work

The Sprint has States with Checkpoints

Sprint in Under Control State (Card Preview)

The Sprint has associated the Work Product Sprint Backlog that contains the set of Product Backlog items selected for the Sprint, and the plan for delivering the product Increment

Under Control (State Card Preview)

26

Scrum Activities
The Scrum events (except the Sprint which is represented as an Alpha) are represented as Activities

Sprint Planning Meeting (Card Preview)

The Sprint Planning Meeting activity provides guidance on how to achieve the Planned state of the Sprint. 27

CONTENTS
Essence

1. IJIs EssWork 2. EssWork Our Approach: Essence

1. Process Orchestration Approach 2. UI Prototyping: Practice Execution 3. Contribution & Differentiator 4. Roadmap

Ideation: Practice/Method Capitalization & Automation with BPM

Executable Practice
Make practices executable by OMG BPMN

Easy Method Composition

Method composition by reconfiguring / multiple Practices (Process library)

Once practices and methods are defined in BPM platform,

Method Execution / Guidance
work distribution dynamic staff resolution Tool integration

Monitoring / Analysis Performance

Performance Analysis on People and Process (Composed Activity Spaces)

29

Business Process Management Approach

BPM Lifecycle

Process People Products SVN Process Asset Eclipse EDMS Test Tool Report Generator

e.g. Scrum Process written in BPMN

Executable Scrum Process

Process is clear

Role is clear

Product is clear
31

Method(Practice) Automation using BPM and ACM

Worklist

Subversive +

Collaboration

KM

Eclipse

Web2.0 Portal
/ /

Process Repository

Practice processes Method processes

BPM/ACM engine

/
CI tools

Requirement Tools
(Mondrian OLAP)

Modeling Tools

Testing Tools

Business Modeling Business Motivation Model Organization Model Business Process Model Business Rule Model

OSS




Alphas, Activity Spaces ( , )

Kernel Composer: Practice Composer: Method Composer = n : nn : nnn : nnnn ? Method Composer Practice Composer, ,

BPMN-based Activity Space Composer

Practice Composer
Kernal Activity Stapces

2e ISP RUP .. Kernal Alphas .. . . ..

Competency

BPMN .

, ,

, .

/


/ ()

(/) () ()

System Architecture
Differentiator : fit for more wide range of end-users

Web 2.0 Technology better UX and bi-directional collaborative work (collective intelligence) Cloud for SaaS service, multi-tenanted, linear scalable Automated integrated with existing ALM tools and BPM Open Source everyone can extend the platform Open Platform everyone can share their practices

36

Vision: Essence Practice Community

E.g. BPMN Community

http://en.bpmn-community.org/

Discussion