ESSENCE-POWERED SCRUM

Transcription

1 ESSENCE-POWERED SCRUM - A GENERIC APPROACH TO DESCRIBING PRACTICES USING ESSENCE KERNEL AND LANGUAGE PROFESSOR JUNE SUNG PARK, KAIST / SEMAT

2 ESSENCE KERNEL 2 Alpha Activity Space Competency

3 Endeavor Solution Customer ALPHA 3 Opportunity <provide Stakeholders Alpha represents things to deal with in any software engineering project. <set up to address focuses> Requirements scopes and constraints> <fulfills use and consume> <produces Software System Support> * Alpha means Abstract-Level Progress Health Attribute. Work <performs and plans Team Way of Working

4 ALPHA STATE AND CHECKLIST 4

5 STATE OF SOFTWARE ENGINEERING PROJECT 5 Oh, I guess it s going OK? How is the project going?

6 STATE OF SOFTWARE ENGINEERING PROJECT 6 Yeah, this is the current state. Really? You re sure?

7 ALPHA DECOMPOSITION AND EXTENSION 7 An alpha may have lower-level, more granule sub-alphas whose states contribute to and drive the state of the super-alpha. Association between super-alphas and sub-alphas can be many-to-many. An alpha may be Extended (i.e., have the values of its attributes be changed) in the context of a Practice (such as Scrum). Alpha Alpha Sub-Alpha Extended Alpha

8 Endeavor Solution Customer ACTIVITY SPACE 8 Activity spaces are containers of activities performed in a project. An activity may be a part of another activity forming a work breakdown structure. The association between activity spaces and activities can be many-to-many. Explore Possibilities Understand Stakeholder Needs Ensure Stakeholder Satisfaction Use the System Understand the Requirements Shape the System Implement the System Test the System Deploy the System Operate the System Prepare to do the Work Coordinate the Activity Support Team Track Progress Stop the Work

9 Identified Solution Needed Value Established Viable Addressed Benefit Accrued Recognized Represented Involved In Agreement Satisfied for Deployment Satisfied in Use ACTIVITY SPACE AND ALPHA STATE 9 Alpha States Opportunity Stakeholder Pre and post conditions of each activity space are suggested (as a reference) in terms of alpha states in the kernel. Activity Spaces Explore Possibilities Understand Stakeholder Needs Ensure Stakeholder Satisfaction Use the System

10 ESSENCE KERNEL EXTENSION 10 Patterns can arrange language elements into arbitrary meaningful structures. Resources can be attached to any language element. Tags add user defined information to any language element. User-Defined Types detail, explain, and constrain the proper usage of particular patterns, resources, or tags.

11 ESSENCE LANGUAGE 11

12 METHOD DESCRIPTION IN ESSENCE LANGUAGE 12 Methods There are probably hundred thousands of methods applied in SE projects worldwide. There are about 300 well known practices reusable across projects. are defined in terms of Custom Method A Practices Custom Method B are composed of Those practices can be described using Essence kernel and language. A project method can be composed of practices. OMG Standard Essence Kernel Essence Language are described using

13 targets> defines / produces / updates> <has defines one way to accomplish > ESSENCE KERNEL AND METHOD 13 Alpha Work Product Work Alpha State Task Activity < defines Approach Activity Space Competency Practice < is composed of Method

14 PRACTICE DESCRIPTION IN ESSENCE LANGUAGE 14 A software engineering practice can be described in Essence language by mapping: work products to Alphas, activities to Activity Spaces roles to Competencies Mapping a practice to Essence produces a mapping from activities to default state transitions. Essence Kernel Alpha Alpha State Activity Space Practice Work Product Activity Competency Role

15 targets> produces / updates> <has ACTIVITY AND STATE TRANSITION 15 Activities may change the alpha states of the software engineering project. Activities can be assigned target alpha states or checkpoints (i.e. criteria of done). By mapping activities to activity spaces you can get default target states of each activity. Alpha Alpha State Activity Space Work Product Activity Competency

16 Endeavor Is qualified to perform> targets> Solution <has produces / updates> Customer COMPETENCY AND ROLE 16 Work Product Stakeholder Representation Alpha organizes> Analysis Development Testing Alpha State Activity Leadership Management Activity Space The role can be modeled as a Pattern. Patterns can arrange language elements into arbitrary meaningful structures. Competency profiles> Role

17 PRACTICE DESCRIPTION APPROACH Build an Ontology of the Terms used in the Practice Parse the text description of the Practice to build a Glossary. Classify the Terms in the Glossary into Work Products, Activities, Roles, etc. Add missing Terms such as activities for producing or updating work products and vice versa. 2. Map the Terms to Essence Language Elements. Determine alphas, alpha states and checkpoints corresponding to each work product. Determine activity spaces, beginning and target alpha states, target checkpoints corresponding to each activity. Determine competencies required of different roles. 3. Decompose and Extend Essence Kernel Elements to represent detailed concepts, composite constructs and complex relationships. Define sub-alphas, sub-activity spaces, patterns, resources and tags to represent concepts in the practice. Build Practice Ontology Map Terms to Essence Language Elements Decompose and Extend Essence Kernel Elements if necessary

18 SCRUM PRACTICE 18 Development Team Task Breakdown Product Increment Jeff Sutherland and Ken Schwaber, The Scrum Guide, (

19 SCRUM GLOSSARY 19 Key Terms Classification Relationship Role Activity Work Product Added Terms Daily Scrum Activity Development Team Sprint Plan, Total Work Remaining Definition of Done Work Product Sprint Retrospective Increment, Product Backlog Refinement Developer Role Development Team Role Daily Scrum Sprint Backlog, Development Work, Increment Development Work Activity Sprint Backlog, Development Work Plan, Work Unit, Development Work Increment Plan Improvement Plan Work Product Sprint Retrospective Increment Work Product Sprint Review Sprint Plan, Sprint Goal, Sprint Backlog, Definition of Done Product Backlog Work Product Product Owner Product Backlog Refinement, Product Backlog Product Backlog Item Sprint Review Creation Product Backlog Item Work Product Product Backlog Product Backlog Refinement Activity Product Backlog Product Owner Role Product Backlog Creation, Product Backlog Product Backlog Refinement, Product Backlog Creation Sprint Review Scrum Event Composite Activity Scrum Master Role Sprint Retrospective Scrum Team Work Product PO, DT, SM Sprint Milestone Sprint Backlog Work Product Development Team Product Backlog, Sprint Goal, Development Work Sprint Goal Work Product Sprint Planning Sprint Planning Sprint Plan Composite Work Product Sprint Planning Activity Sprint Plan Sprint Retrospective Activity Scrum Master Sprint Plan, Definition of Done, Sprint Review Activity Stakeholders, Increment, Product Backlog, Total Work Remaining, Sprint Plan Stakeholders Role Sprint Review Total Work Remaining Work Product Sprint Review, Daily Scrum Work Unit Work Product Sprint Backlog, Development Work

20 SCRUM ONTOLOGY 20

21 SCRUM TO ESSENCE KERNEL MAPPING 21 Scrum Explore Possibilities Opportunity Requirements Product Backlog Sprint Goal Sprint Backlog Definition of Done Product Backlog Item Understand Stakeholder Needs Understand the Requirements Shape the System Implement the System Product Backlog Creation Product Backlog Refinement Development Work Software System Increment Test the System Work Development Work Plan Work Unit Coordinate the Activity Sprint Planning Total Work Remaining Track Progress Daily Scrum Team Scrum Team Ensure Stakeholder Satisfaction Sprint Review Way of Working Improvement Plan Support the Team Sprint Retrospective

22 COMPOSITE CONSTRUCTS IN SCRUM 22 Sprint Planning produces Sprint Plan Sprint Goal Conducts Development Work Scrum Event Daily Scrum may change Sprint Backlog Development Work Plan Product Backlog Item Work Unit Sprint Produces Increment Sprint Review provides input to Sprint Retrospective Manages Product Backlog Product Owner Performs Scrum Team Development Team Creates Ensures enactment of Scrum Scrum Master

23 WORK PRODUCT TO ALPHA STATE MAPPING 23 Alpha State Work Product Alpha Begin In Target Product Backlog Requirements Bounded Acceptable Opportunity Solution Needed Viable Sprint Goal Requirements Bounded Coherent Sprint Backlog Requirements Coherent Acceptable Definition of Done Requirements Acceptable Fulfilled Development Work Plan Work Initiated Prepared Increment Software System Architecture Selected Ready Work Prepared Concluded Total Work Remaining Work Started Under Control Scrum Team Team Seeded Performing Improvement Plan Way of Working Foundation Established Working Well

24 WORK PRODUCT TO ALPHA STATE MAPPING 24 Product Backlog Sprint Goal Increment Dev Work Plan Increment Scrum Team Improve Plan Sprint Backlog TWR Definition of Done

25 WORK PRODUCT DEFINITION CARD 25 Sprint Backlog Scrum Practice Product Backlog Item Development Work Plan Work Unit Understand Stakeholder Needs Understand the Requirements Coordinate the Activity Sprint Planning Requirements Coherent Acceptable The stakeholders accept that the requirements describe an acceptable solution. The rate of change to the agreed requirements is relatively low and under control. The value provided by implementing the requirements is clear. The parts of the opportunity satisfied by the requirements are clear. The requirements are testable. Work Initiated Prepared Commitment is made. Cost and effort of the work are estimated. Resource availability is understood. Governance policies and procedures are clear. Risk exposure is understood. Acceptance criteria are defined and agreed with client. The work is broken down sufficiently for productive work to start. Tasks have been identified and prioritized by the team and stakeholders. A credible plan is in place. Funding to start the work is in place. The team or at least some of the team members are ready to start the work. Integration and delivery points are defined.

26 Identified Solution Needed Value Established Viable Addressed Benefit Accrued Conceived Bounded Coherent Acceptable Addressed Fulfilled Architecture Selected Demonstrable Usable Ready Operational Retired Seeded Formed Collaborating Performing Adjourned Initiated Prepared Started Under Control Concluded Closed Principles Established Foundation Established In Use In Place Working Well Retired ACTIVITY TO ALPHA STATE MAPPING 26 Activity Activity Spaces Alpha States Opportunity Requirement Software System Team Work Way of Working Product Backlog Creation Product Backlog Refinement Sprint Planning Development Work Daily Scrum Sprint Review Sprint Retro. Explore Possibilities Understand Reqts Understand St. Needs Understand Reqts Understand St. Needs Understand Reqts Coordinate Activity Shape the System Implement / Test Track Progress Ensure St. Satisfaction Track Progress Support the Team

27 ACTIVITY DEFINITION CARD 27 Sprint Review Scrum Practice Ensure Stakeholder Satisfaction Track Progress Product Owner Development Team Scrum Master Sprint Goal Sprint Backlog Increment Stakeholder Product Backlog Opportunity Viable Addressed A usable system that demonstrably addresses the opportunity is available. The stakeholders agree that the available solution is worth deploying. The stakeholders are satisfied that the solution produced addresses the opportunity. Work Under Control Concluded All outstanding tasks are administrative housekeeping or related to preparing the next piece of work. Work results have been achieved. The stakeholders have accepted the resulting software system.

28 SCRUM WORKFLOW 28

29 METHOD COMPOSITION 29 Scrum Stakeholder Explore Possibilities Agile Modeling Opportunity Requirements Software System Work Opportunity Product Backlog Sprint Goal Sprint Backlog Definition of Done Software Requirement Model Increment Software Architecture Development Work Plan Business Product Requirements Backlog Item Work Unit Understand Stakeholder Needs Understand the Requirements Shape the System Implement the System Test the System Coordinate the Activity Business Analysis Product Backlog Creation Product Backlog Refinement Spike Development Model Storming Work Sprint Planning Total Work Remaining Track Progress Daily Scrum Team Scrum Team Ensure Stakeholder Satisfaction Sprint Review Way of Working Improvemen t Plan Support the Team Sprint Retrospective

30 METHOD COMPOSITION 30 Kernel elements covered by Scrum Kernel elements additionally covered by Agile Modeling Add XP Add Dev Ops Add SPM

31 CONCLUSION We d better learn and use Essence. I think so, too. It really makes 31 defining and using methods easy. You can use Essence kernel to: Describe practices Merge them into a project method Monitor health and progress of the project Adaptively determine project goals and activities based on the current state assessment.