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

Transcription

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

2 SSENCE KERNEL 2 Alpha Activity Space Competency

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

4 LPHA STATE AND CHECKLIST 4

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

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

7 LPHA 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 c an 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 CTIVITY 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. Customer Explore Possibili+es Understand Stakeholder Needs Ensure Stakeholder Sa+sfac+on Use the System Solu+on Understand the Requirements Shape the System Implement the System Test the System Deploy the System Operate the System Endeavor Prepare to do the Work Coordinate the Ac+vity Support Team Track Progress Stop the Work

9 CTIVITY SPACE AND ALPHA STATE 9 Alpha States Opportunity Stakeholder Pre and post conditions of each activity space are sugg ested (as a reference) in ter ms of alpha states in the ke rnel. Ac+vity Spaces Explore Possibili+es Understand Stakeholder Needs Iden+fied Solu+on Needed Value Established Viable Addressed Benefit Accrued Recognized Represented Involved In Agreement Sa+sfied for Deployment Sa+sfied Ensure Stakeholder Sa+sfac+on Use the System

10 SSENCE KERNEL EXTENSION 10 Patterns can arrange language ele ments into arbitrary meaningful st ructures. 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 o f particular patterns, resources, or tags.

11 SSENCE LANGUAGE 11

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

13 SSENCE KERNEL AND METHOD 13 Alpha organizes> Work Product Work <has Alpha State <evidences is progressed by > defines / produces / updates> Task targets> < defines organizes> Activity Approach Activity Space <requires < is composed of Competency Practice Method

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

15 CTIVITY AND STATE TRANSITION 15 Activities may change the alpha states of t he software engineering project. Alpha <has organizes> <evidences Work Product Activities can be assigned target alpha stat es or checkpoints (i.e. criteria of done). By mapping activities to activity spaces yo u can get default target states of each ac tivity. Alpha State targets> is progressed by > organizes> produces / updates> Ac7vity Ac7vity Space Competency

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

17 RACTICE DESCRIPTION APPROACH 17. 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.. 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 corresp onding to each activity. Determine competencies required of different roles.. Decompose and Extend Essence Kernel Elements to represent detaile d concepts, composite constructs and complex relationships. Define sub-alphas, sub-activity spaces, patterns, resources and tags to represent c oncepts in the practice. Build Practice Ontology Map Terms to Essence Language Elements Decompose and Extend Essence Kernel Elements if necessary

18 CRUM PRACTICE 18 Development Team Task Breakdow n Product Increment Jeff Sutherland and Ken Schwaber, The Scrum Guide, (

19 CRUM GLOSSARY 19 Key Terms Classification Relationship Role Activity Work Product Added Terms Scrum Activity Development Team Sprint Plan, Total Work Remaining nition of Done Work Product Sprint Retrospective Increment, Product Backlog Refinement eloper Role elopment Team Role Daily Scrum Sprint Backlog, Development Work, Increment elopment Work Activity Sprint Backlog, Development Work Plan, Work Unit, Incre Development Work ment an ovement Plan Work Product Sprint Retrospective ment Work Product Sprint Review Sprint Plan, Sprint Goal, Sprint Backlog, Definition of Done uct Backlog Work Product Product Owner Product Backlog Refinement, S Product Backlog Cr Product Backlog Item print Review ion uct Backlog Item Work Product Product Backlog uct Backlog Refinement Activity Product Backlog uct Owner Role Product Backlog Creation, Pro Product Backlog Cr duct Backlog Refinement, Sprin Product Backlog ion t Review m Event Composite Activity m Master Role Sprint Retrospective m Team Work Product PO, DT, SM t Milestone t Backlog Work Product Development Team Product Backlog, Sprint Goal, Development Work t Goal Work Product Sprint Planning Sprint Planning t Plan Composite Work Product t Planning Activity Sprint Plan t Retrospective Activity Scrum Master Sprint Plan, Definition of Done, t Review Activity Stakeholders, Increment, Product Backlog, Total Work Remaining, Sprint Plan eholders Role Sprint Review l Work Remaining Work Product Sprint Review, Daily Scrum k Unit Work Product Sprint Backlog, Development Work

20 CRUM ONTOLOGY 20

21 CRUM 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 OMPOSITE CONSTRUCTS IN SCRUM 22 Sprint Planning produces Sprint Plan Sprint Goal Development Work Daily Scrum may change Sprint Backlog Product Backlog Item Conducts Scrum Event Development Work Plan Work Unit rint Produces Increment Sprint Review provides input to Sprint Retrospective m Team Manages Product Backlog Product Owner Performs Development Team Creates Ensures enactment of Scrum Scrum Master

23 ORK PRODUCT TO ALPHA STATE MAPPING 23 Alpha State Work Product Alpha Begin In Target roduct Backlog Requirements Bounded Acceptable Opportunity Solution Needed Viable print Goal Requirements Bounded Coherent print Backlog Requirements Coherent Acceptable efinition of Done Requirements Acceptable Fulfilled evelopment Work Plan Work Initiated Prepared crement Software System Architecture Selected Ready Work Prepared Concluded otal Work Remaining Work Started Under Control crum Team Team Seeded Performing provement Plan Way of Working Foundation Established Working Well

24 ORK 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 ORK 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 CTIVITY TO ALPHA STATE MAPPING 26 ctivity roduct acklog reation roduct acklog finement Sprint lanning elopment Work ily Scrum Sprint Review int Retro. Alpha States Activity Spaces 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 Identified Opportunity Requirement Software System Team Work Way of Working 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

27 CTIVITY DEFINITION CARD 27 Sprint Review Scrum Practice Ensure Stakeholder Satisfaction Track Progress Product Owner Development Team Scrum Master Stakeholder Sprint Goal Sprint Backlog Increment 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 CRUM WORKFLOW 28

29 ETHOD COMPOSITION 29 Scrum Stakeholder Explore Possibilities gile deling 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 Improvement Plan Support the Team Sprint Retrospective

30 ETHOD COMPOSITION 30 Kernel elements covered by Scrum Kernel elements additionally covered by Agile Modeling Add XP Ad De Op Add SPM

31 ONCLUSION We d better learn and use Essence. I think so, too. It really makes 31 defining and using methods easy. ou 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.