drive project with essence
TRANSCRIPT
THE ESSENCE OF SOFTWARE ENGINEERING
DRIVE PROJECTS WITH ESSENCE
SUMMARY
Goals
SEMAT Kernel
Dimensions
Alphas
In Action
GOALS
Improve software engineering quality
Use a common & actionable framework
Build best practices on a standard core
Drive projects on all aspects
SEMAT KERNEL
Captures the essence of software engineering
Forms a map of the software engineering context
Constitutes a basis for evaluating on-going work
3 DIMENSIONS
‣Customer
‣System
‣Endeavor
ALPHA
“An essential element of the software engineering endeavor that is relevant to an assessment of the progress and health of the endeavor”
‣Each dimension is assessed on its alphas
‣ An Alpha has multiple states
CUSTOMER
‣OPPORTUNITY
“The set of circumstances that makes it appropriate to develop or change a software system”
‣STAKEHOLDER
“The people, groups or organizations who affect or are affected by a software system”
CUSTOMER
Value Established
Viable
Addressed
Benefits Accrued
Identified Stakeholders identified the opportunity
Solution Needed Problem, root causes, needs
Value and Impact understood
Feasibility, Risks, Constraints
Produced, Usable, Worth deployingOperational, Beneficial, ROI >= expected
OPPORTUNITY
CUSTOMER
STAKEHOLDERS
Represented
Involved
In Agreement
Satisfied for Deployment
Satisfied In Use
Recognized Group and ResponsibilitiesCollaboration approach, Way of workingFeedback, Decisions, CommunicationInputs, Priorities and Expectations
Stakeholder give feedback and GO LiveSystem meets or exceed expectations
SOLUTION
‣REQUIREMENTS
“What the software system must do to address the opportunity and satisfy the stakeholders”
‣SOFTWARE SYSTEM
“A system made up of software, hardware and data that provides its primary value by the execution of the software.”
SYSTEM
REQUIREMENTS
Conceived
Bounded
Coherent
Acceptable
Addressed
Fullfilled
Need, Users, SponsorsPurpose, Success, Scope, MechanismsMain scenarios, Priorities, Conflict ResolutionDescription acceptable, Change lowImplemented enough, Worth operatingSatisfied by the software system
SYSTEM
SOFTWARE SYSTEM
Arch. Selected
Demonstrable
Usable
Ready
Operational
Retired
Architecture, platforms, technologiesArchitecture demonstrated and testableDesired quality, tested, acceptableDocumented, accepted by stakeholdersIn use and available
No longer supported, discontinued
ENDEAVOR
‣TEAM
“People engaged in the development, maintenance, delivery, support of a specific software”
‣WORK
“Activity done in order to achieve result”
‣WAY OF WORKING
“Tailored set of practices and tools used by a team”
ENDEAVOR
TEAM
Seeded
Formed
Collaborating
Performing
Adjourned
Mission and skills identifiedResources and responsibilities definedWorking as one unit, open communicationEfficient, adapt to change, high qualityResponsibilities handed over
ENDEAVOR
WORK
Initiated
Prepared
Started
Under Control
Concluded
Closed
Mission and skills identified
Resources and responsibilities definedWorking as one unit, open communicationEfficient, adapt to change, high qualityEnough is implemented, system operational
Satisfied by the software system
ENDEAVOR
WAY OF WORKING
Principles Established
Foundation Established
In Use
In Place
Working Well
Retired
Mission and skills identified
Resources and responsibilities definedWorking as one unit, open communicationEfficient, adapts to change, high qualityEnough is implemented, system operationalSatisfied by the software system
IN ACTION
‣Experimentation in JIRA
‣Define new issue types for each alpha
‣Define state and workflow for each alpha
‣Create “boards” to act on and monitor workflow
