Software Extension To The Pmbok Guide Fifth Edition 1e5j11
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report r6l17
Overview 4q3b3c
& View Software Extension To The Pmbok Guide Fifth Edition as PDF for free.
More details 26j3b
- Words: 2,021
- Pages: 31
S2EA
SWX: The Software Extension to the PMBOK Guide® for Project Management prepared and presented by Richard E. (Dick) Fairley, PhD, CSDP Software and Systems Engineering Associates (S2EA)
SWX Software Extension
STC – 10 April 2013
slide 1
Agenda
S2EA
• • • • • • •
SWX Software Extension
What is SWX? Why a software extension? Key elements of SWX The process Current status Lessons learned Questions?
STC – 10 April 2013
slide 2
S2EA
What is SWX?
• SWX is an adaptation and extension of A Guide to the Project Management Body of Knowledge (PMBOK® Guide) • SWX is a t project of the IEEE Computer Society (CS) and the Project Management Institute (PMI) o a ten-member team; 5 from each organization o the first t endeavor by each organization o copyright will be shared by the CS and PMI
SWX Software Extension
STC – 10 April 2013
slide 3
S2EA
SWX Software Extension
SWX Team
STC – 10 April 2013
slide 4
S2EA
Why a Software Extension?
• The PMBOK® Guide is a generic document o intended as guidance for managing all kinds of projects • More than 65% of the 400K+ of PMI identify their work as IT or software related • The mission of the CS is to develop products and services for the ~100K o primarily through the Professional Activities Board • Other PMBOK® extensions include: o the construction extension o the government extension
SWX Software Extension
STC – 10 April 2013
slide 5
S2EA
Why a Software Extension? (2)
• Software is an intangible product o which lends itself to a variety of development approaches o unlike physical products • Software developers are knowledge workers o who develop innovative solutions to new problems o by sharing knowledge and outcomes in a closely coordinated learning environment
SWX Software Extension
STC – 10 April 2013
slide 6
S2EA
Why a Software Extension? (3)
• Traditional project managers will learn about methods, tools, and techniques for managing software projects o what’s the same; what’s different? • Software project managers and practitioners will learn how traditional methods of project management can be tailored for software projects o what can we learn and apply?
SWX Software Extension
STC – 10 April 2013
slide 7
S2EA
Why a Software Extension? (4) “managing a large computer programming project is like managing any other large undertaking—in more ways than most programmers believe. But in many ways it is different— in more ways than most professional managers expect” The Mythical Man-Month, Anniversary Edition, Frederick P. Brooks, Jr., Addison Wesley, 1995; pp. x.
SWX Software Extension
STC – 10 April 2013
slide 8
S2EA
The PMBOK® Guide
• The PMBOK® Guide – Fifth Edition has just been released • It includes 47 processes grouped into 10 knowledge areas o each process is described by • Inputs, • Tools and Techniques, and • Outputs • The PMBOK® Guide is a guide to the BOK, not the BOK o it includes commonly accepted good practices o but does not attempt to cover every possible situation • The PMBOK® Guide is about 500 pages in length SWX Software Extension
STC – 10 April 2013
slide 9
S2EA
A Key Statement in the PMBOK® Guide
• From Section 2.4 of the PMBOK® Guide – Fifth Edition “Project life cycles can be described as falling somewhere in a continuum from predictive or plan-driven approaches at one end to adaptive or change-driven approaches at the other.” • As modified in SWX: “Software project life cycles can be described as falling somewhere in a continuum from highly predictive approaches at one end to highly adaptive approaches at the other.” • Note: o adaptive projects also have plans o predictive projects also have changes
SWX Software Extension
STC – 10 April 2013
slide 10
S2EA
SWX Figure 2-1 Highly Predictive
Predictive
Adaptive
• Requirements are • Requirements are specified during elaborated at periodic initiation and intervals during planning software development • Risk and cost are • Risk and cost are controlled by detailed controlled by planning based on inprogressively detailed depth analysis of planning based on requirements and timely specification of constraints prior to requirements and development constraints during • Key stakeholders are development involved at scheduled • Key stakeholders are milestones involved at specified intervals
SWX Software Extension
STC – 10 April 2013
Highly Adaptive
• Requirements are elaborated at frequent intervals during software development • Risk and cost controlled as requirements and constraints emerge • Key stakeholders are continuously involved
slide 11
S2EA
The Ten Knowledge Areas in PMBOK and SWX
Integration Management Scope Management Time Management Cost Management Quality Management
Human Resource Management Communications Management Risk Management Procurement Management Stakeholder Management
The Life Cycle Continuum is not a thin straight line All SDLCs are multi-dimensional The processes in each KA must be tailored for the chosen SDLC
SWX Software Extension
STC – 10 April 2013
slide 12
S2EA
Four Orthogonal Concepts: BUP vs BPD vs ID vs IC
• A predictive life cycle project may involve Big Upfront Planning (BUP) o but can avoid Big Product Delivery (BPD) • by doing Incremental Development (ID) o to produce increments of working software that can be demo’d and delivered into the operational environment • Iterative Cycles (IC) can be used across the continuum o to produce deliverable increments on some iterations o to produce internal-demo increments on other iterations o to produce no increments on still other iterations • ID may or may not use IC SWX Software Extension
STC – 10 April 2013
slide 13
S2EA
A Primary Contribution of SWX
• A primary contribution of SWX is tailoring and adaptation of the 47 processes in the PMBOK Guide for adaptive software project life cycles o because many of the processes in the PMBOK Guide are applicable to management of predictive life cycle software projects • and are referenced but not repeated in SWX o and because the PMBOK Guide includes a discussion of “adaptive” but merges IC with ID o and does not discuss tailoring of the 47 processes for different life cycles SWX Software Extension
STC – 10 April 2013
slide 14
S2EA
A Predictive Software Project Life Cycle
Analyze Architect Design Construct Integrate Test
time SWX Software Extension
STC – 10 April 2013
slide 15
S2EA
The Five Process Groups of the PMBOK® Guide
SWX Software Extension
STC – 10 April 2013
slide 16
S2EA
Incremental Development
Analyze Architect
Feature Set 1
Design Construct & Integrate
Feature Set 2
Demo Working Product 1
Test
Design Construct & Integrate
Feature Set 3
Test
Design Construct & Integrate
Feature Set 4
Demo Working Product 1&2
Test
Design Construct & Integrate
Demo Working Product 1, 2, & 3
Test
Demo Working Product 1, 2, 3, & 4
time
SWX Software Extension
STC – 10 April 2013
slide 17
S2EA
Adaptability versus Agility • “agile” is an overloaded term o and is not used in SWX o Various adaptive life cycles include various aspects of agility o aspects of agility are listed and referred to throughout SWX
SWX Software Extension
STC – 10 April 2013
slide 18
S2EA
Aspects of Agility in Adaptive SDLCs
• Increments of working deliverable software are produced on some iteration cycles o increments and iterations are distinct concepts • Durations of adaptive iteration cycles vary from daily to weekly to monthly, but usually not more than monthly • Adaptive iteration cycles are often of the same duration (i.e., are “time boxed”) but some cycles may be of longer or shorter duration by exception • Requirements, design, and the software product emerge as the project evolves
SWX Software Extension
STC – 10 April 2013
slide 19
S2EA
Aspects of Agility in Adaptive SDLCs (2) • Multi-stage Iterations o Iterations can incorporate as many software development stages as desired (from Analyze to Test) • Vertical Slices o increments of delivered functionality include as many architecture components as desired
SWX Software Extension
STC – 10 April 2013
slide 20
S2EA
Aspects of Agility in Adaptive SDLCs (3)
• Adaptive software development teams are small o 10 or fewer o large projects include multiple small teams • All of each software development team are assigned to one project at a time • Each software development team includes the generalists and specialists needed to develop the product (cross-functional teams) o experts (functional and domain) may be involved periodically or as needed Adaptive software teams are self-organizing and self-directed SWX Software Extension
STC – 10 April 2013
slide 21
S2EA
Aspects of Agility in Adaptive SDLCs (4)
• A customer, customer’s representative, and/or knowledgeable is involved on a continuing basis o observes periodic demonstrations of working deliverable software (on a daily, weekly, bi-weekly, or monthly basis) o provides guidance for further product development The customer is responsible for project and product scope
SWX Software Extension
STC – 10 April 2013
slide 22
S2EA
A Pattern for Adaptive Software Development Life Cycles Product Vision Product Feature Set
Daily standup meetings & frequent demos Iteration Feature Design Construct Product Set Increment frequent internal iterations
Product Planning
Iteration Planning
Demo
Test
Demo Working Software
Demonstration and Review
Internal Iterations Initial Product Planning
SWX Software Extension
External Iterations
STC – 10 April 2013
slide 23
A Quote from SWX (for the previous figure)
S2EA
“A generic example of a software development method for an adaptive software project life cycle is illustrated in Figure 2-5. This is a common software development pattern, often used as a basis for agile development methods. Examples that use variations of this pattern include Scrum, eXtreme Programming, Feature-Driven Development, TestDriven Development, and the Dynamic System Development Method.” SWX Software Extension
STC – 10 April 2013
slide 24
Internals of an Adaptive SDLC with Test-Driven Development (TDD)
S2EA
specify requirement(s)
select next feature
frequent iterations & daily standups
Team
demonstrate capabilities
write test scenarios
test, add new features, test, refactor
potential product delivery
SWX Software Extension
STC – 10 April 2013
TDD
slide 25
A Highly Adaptive SDLC
S2EA
team hears customer story
team discusses options with customer
team writes test scenarios
daily iterations
customer
team demonstrates capabilities potential product delivery
SWX Software Extension
team adds new features, tests, and refactors
STC – 10 April 2013
slide 26
S2EA
Typical practices of internal adaptive and external highly adaptive software projects
SWX Software Extension
STC – 10 April 2013
slide 27
S2EA
The SWX Process (1)
• Proposal submitted to the Computer Society and PMI: July 2010 o lawyers argue • SWX Committee formed: August 2011 • SME draft prepared: August 2011 – July 2012 • SME draft review: July 2012 o 27 SME respondents; 730 recommendations • Public exposure draft prepared: August – November 2012 • Exposure draft review: 10 December 2012 – 10 January 2013 o 170 respondents; 1973 recommendations • Individual and team consensus reviews: 11 January – 25 March 2013 SWX Software Extension
STC – 10 April 2013
slide 28
S2EA
The SWX Process (2)
Reviewers notified: 25 March 2013 Reviewer’s appeals received: 1 April 2013 Rewrite period: 25 March – 8 April 2013 Copy editing: 9 April – 7 May 2013 Committee reviews/ballots: 7 May – 21 May 2013 PMI & Computer Society review and approval: o June – August 2013 • Publication date: o electronic: August 2013; print: September 2013 • • • • • •
SWX Software Extension
STC – 10 April 2013
slide 29
Lessons Learned
S2EA
• It’s always more work than you think it will be • Avoiding personal ownership of written material is hard o egoless writing? • Good mix of team skills (cross functional) was important • Real world experience of team was essential • Partnership between CS and PMI working well • Four f2f meetings at six month intervals was good o a couple closer in beginning would have helped the team to jell faster o f2f meetings contributed to a collaborative learning experience o and resulted in a better product SWX Software Extension
STC – 10 April 2013
slide 30
S2EA
Questions?
SWX Software Extension
STC – 10 April 2013
slide 31
SWX: The Software Extension to the PMBOK Guide® for Project Management prepared and presented by Richard E. (Dick) Fairley, PhD, CSDP Software and Systems Engineering Associates (S2EA)
SWX Software Extension
STC – 10 April 2013
slide 1
Agenda
S2EA
• • • • • • •
SWX Software Extension
What is SWX? Why a software extension? Key elements of SWX The process Current status Lessons learned Questions?
STC – 10 April 2013
slide 2
S2EA
What is SWX?
• SWX is an adaptation and extension of A Guide to the Project Management Body of Knowledge (PMBOK® Guide) • SWX is a t project of the IEEE Computer Society (CS) and the Project Management Institute (PMI) o a ten-member team; 5 from each organization o the first t endeavor by each organization o copyright will be shared by the CS and PMI
SWX Software Extension
STC – 10 April 2013
slide 3
S2EA
SWX Software Extension
SWX Team
STC – 10 April 2013
slide 4
S2EA
Why a Software Extension?
• The PMBOK® Guide is a generic document o intended as guidance for managing all kinds of projects • More than 65% of the 400K+ of PMI identify their work as IT or software related • The mission of the CS is to develop products and services for the ~100K o primarily through the Professional Activities Board • Other PMBOK® extensions include: o the construction extension o the government extension
SWX Software Extension
STC – 10 April 2013
slide 5
S2EA
Why a Software Extension? (2)
• Software is an intangible product o which lends itself to a variety of development approaches o unlike physical products • Software developers are knowledge workers o who develop innovative solutions to new problems o by sharing knowledge and outcomes in a closely coordinated learning environment
SWX Software Extension
STC – 10 April 2013
slide 6
S2EA
Why a Software Extension? (3)
• Traditional project managers will learn about methods, tools, and techniques for managing software projects o what’s the same; what’s different? • Software project managers and practitioners will learn how traditional methods of project management can be tailored for software projects o what can we learn and apply?
SWX Software Extension
STC – 10 April 2013
slide 7
S2EA
Why a Software Extension? (4) “managing a large computer programming project is like managing any other large undertaking—in more ways than most programmers believe. But in many ways it is different— in more ways than most professional managers expect” The Mythical Man-Month, Anniversary Edition, Frederick P. Brooks, Jr., Addison Wesley, 1995; pp. x.
SWX Software Extension
STC – 10 April 2013
slide 8
S2EA
The PMBOK® Guide
• The PMBOK® Guide – Fifth Edition has just been released • It includes 47 processes grouped into 10 knowledge areas o each process is described by • Inputs, • Tools and Techniques, and • Outputs • The PMBOK® Guide is a guide to the BOK, not the BOK o it includes commonly accepted good practices o but does not attempt to cover every possible situation • The PMBOK® Guide is about 500 pages in length SWX Software Extension
STC – 10 April 2013
slide 9
S2EA
A Key Statement in the PMBOK® Guide
• From Section 2.4 of the PMBOK® Guide – Fifth Edition “Project life cycles can be described as falling somewhere in a continuum from predictive or plan-driven approaches at one end to adaptive or change-driven approaches at the other.” • As modified in SWX: “Software project life cycles can be described as falling somewhere in a continuum from highly predictive approaches at one end to highly adaptive approaches at the other.” • Note: o adaptive projects also have plans o predictive projects also have changes
SWX Software Extension
STC – 10 April 2013
slide 10
S2EA
SWX Figure 2-1 Highly Predictive
Predictive
Adaptive
• Requirements are • Requirements are specified during elaborated at periodic initiation and intervals during planning software development • Risk and cost are • Risk and cost are controlled by detailed controlled by planning based on inprogressively detailed depth analysis of planning based on requirements and timely specification of constraints prior to requirements and development constraints during • Key stakeholders are development involved at scheduled • Key stakeholders are milestones involved at specified intervals
SWX Software Extension
STC – 10 April 2013
Highly Adaptive
• Requirements are elaborated at frequent intervals during software development • Risk and cost controlled as requirements and constraints emerge • Key stakeholders are continuously involved
slide 11
S2EA
The Ten Knowledge Areas in PMBOK and SWX
Integration Management Scope Management Time Management Cost Management Quality Management
Human Resource Management Communications Management Risk Management Procurement Management Stakeholder Management
The Life Cycle Continuum is not a thin straight line All SDLCs are multi-dimensional The processes in each KA must be tailored for the chosen SDLC
SWX Software Extension
STC – 10 April 2013
slide 12
S2EA
Four Orthogonal Concepts: BUP vs BPD vs ID vs IC
• A predictive life cycle project may involve Big Upfront Planning (BUP) o but can avoid Big Product Delivery (BPD) • by doing Incremental Development (ID) o to produce increments of working software that can be demo’d and delivered into the operational environment • Iterative Cycles (IC) can be used across the continuum o to produce deliverable increments on some iterations o to produce internal-demo increments on other iterations o to produce no increments on still other iterations • ID may or may not use IC SWX Software Extension
STC – 10 April 2013
slide 13
S2EA
A Primary Contribution of SWX
• A primary contribution of SWX is tailoring and adaptation of the 47 processes in the PMBOK Guide for adaptive software project life cycles o because many of the processes in the PMBOK Guide are applicable to management of predictive life cycle software projects • and are referenced but not repeated in SWX o and because the PMBOK Guide includes a discussion of “adaptive” but merges IC with ID o and does not discuss tailoring of the 47 processes for different life cycles SWX Software Extension
STC – 10 April 2013
slide 14
S2EA
A Predictive Software Project Life Cycle
Analyze Architect Design Construct Integrate Test
time SWX Software Extension
STC – 10 April 2013
slide 15
S2EA
The Five Process Groups of the PMBOK® Guide
SWX Software Extension
STC – 10 April 2013
slide 16
S2EA
Incremental Development
Analyze Architect
Feature Set 1
Design Construct & Integrate
Feature Set 2
Demo Working Product 1
Test
Design Construct & Integrate
Feature Set 3
Test
Design Construct & Integrate
Feature Set 4
Demo Working Product 1&2
Test
Design Construct & Integrate
Demo Working Product 1, 2, & 3
Test
Demo Working Product 1, 2, 3, & 4
time
SWX Software Extension
STC – 10 April 2013
slide 17
S2EA
Adaptability versus Agility • “agile” is an overloaded term o and is not used in SWX o Various adaptive life cycles include various aspects of agility o aspects of agility are listed and referred to throughout SWX
SWX Software Extension
STC – 10 April 2013
slide 18
S2EA
Aspects of Agility in Adaptive SDLCs
• Increments of working deliverable software are produced on some iteration cycles o increments and iterations are distinct concepts • Durations of adaptive iteration cycles vary from daily to weekly to monthly, but usually not more than monthly • Adaptive iteration cycles are often of the same duration (i.e., are “time boxed”) but some cycles may be of longer or shorter duration by exception • Requirements, design, and the software product emerge as the project evolves
SWX Software Extension
STC – 10 April 2013
slide 19
S2EA
Aspects of Agility in Adaptive SDLCs (2) • Multi-stage Iterations o Iterations can incorporate as many software development stages as desired (from Analyze to Test) • Vertical Slices o increments of delivered functionality include as many architecture components as desired
SWX Software Extension
STC – 10 April 2013
slide 20
S2EA
Aspects of Agility in Adaptive SDLCs (3)
• Adaptive software development teams are small o 10 or fewer o large projects include multiple small teams • All of each software development team are assigned to one project at a time • Each software development team includes the generalists and specialists needed to develop the product (cross-functional teams) o experts (functional and domain) may be involved periodically or as needed Adaptive software teams are self-organizing and self-directed SWX Software Extension
STC – 10 April 2013
slide 21
S2EA
Aspects of Agility in Adaptive SDLCs (4)
• A customer, customer’s representative, and/or knowledgeable is involved on a continuing basis o observes periodic demonstrations of working deliverable software (on a daily, weekly, bi-weekly, or monthly basis) o provides guidance for further product development The customer is responsible for project and product scope
SWX Software Extension
STC – 10 April 2013
slide 22
S2EA
A Pattern for Adaptive Software Development Life Cycles Product Vision Product Feature Set
Daily standup meetings & frequent demos Iteration Feature Design Construct Product Set Increment frequent internal iterations
Product Planning
Iteration Planning
Demo
Test
Demo Working Software
Demonstration and Review
Internal Iterations Initial Product Planning
SWX Software Extension
External Iterations
STC – 10 April 2013
slide 23
A Quote from SWX (for the previous figure)
S2EA
“A generic example of a software development method for an adaptive software project life cycle is illustrated in Figure 2-5. This is a common software development pattern, often used as a basis for agile development methods. Examples that use variations of this pattern include Scrum, eXtreme Programming, Feature-Driven Development, TestDriven Development, and the Dynamic System Development Method.” SWX Software Extension
STC – 10 April 2013
slide 24
Internals of an Adaptive SDLC with Test-Driven Development (TDD)
S2EA
specify requirement(s)
select next feature
frequent iterations & daily standups
Team
demonstrate capabilities
write test scenarios
test, add new features, test, refactor
potential product delivery
SWX Software Extension
STC – 10 April 2013
TDD
slide 25
A Highly Adaptive SDLC
S2EA
team hears customer story
team discusses options with customer
team writes test scenarios
daily iterations
customer
team demonstrates capabilities potential product delivery
SWX Software Extension
team adds new features, tests, and refactors
STC – 10 April 2013
slide 26
S2EA
Typical practices of internal adaptive and external highly adaptive software projects
SWX Software Extension
STC – 10 April 2013
slide 27
S2EA
The SWX Process (1)
• Proposal submitted to the Computer Society and PMI: July 2010 o lawyers argue • SWX Committee formed: August 2011 • SME draft prepared: August 2011 – July 2012 • SME draft review: July 2012 o 27 SME respondents; 730 recommendations • Public exposure draft prepared: August – November 2012 • Exposure draft review: 10 December 2012 – 10 January 2013 o 170 respondents; 1973 recommendations • Individual and team consensus reviews: 11 January – 25 March 2013 SWX Software Extension
STC – 10 April 2013
slide 28
S2EA
The SWX Process (2)
Reviewers notified: 25 March 2013 Reviewer’s appeals received: 1 April 2013 Rewrite period: 25 March – 8 April 2013 Copy editing: 9 April – 7 May 2013 Committee reviews/ballots: 7 May – 21 May 2013 PMI & Computer Society review and approval: o June – August 2013 • Publication date: o electronic: August 2013; print: September 2013 • • • • • •
SWX Software Extension
STC – 10 April 2013
slide 29
Lessons Learned
S2EA
• It’s always more work than you think it will be • Avoiding personal ownership of written material is hard o egoless writing? • Good mix of team skills (cross functional) was important • Real world experience of team was essential • Partnership between CS and PMI working well • Four f2f meetings at six month intervals was good o a couple closer in beginning would have helped the team to jell faster o f2f meetings contributed to a collaborative learning experience o and resulted in a better product SWX Software Extension
STC – 10 April 2013
slide 30
S2EA
Questions?
SWX Software Extension
STC – 10 April 2013
slide 31
Related Documents 171j1w
Software Extension To The Pmbok Guide Fifth Edition 1e5j11
December 2019 51
The 5th Edition Pmbok Guide a65v
April 2023 0
Guide To Networking Essentials Fifth Edition 73n2h
April 2022 0
Pmbok Guide 6 Vs Pmbok Guide 5 4l5q50
November 2022 0
Pmbok Guide 5th Edition - Notes (2) 19334z
October 2019 67
Pmbok 6th Edition -itto 3g2x35
December 2019 1,080More Documents from "Smith Steve" 6f4j6l
Felicity By Sungha Jung 1c5u1g
November 2019 73
Teenage Mutant Ninja Turtles - Palladium - Accessory - Rpg Accessory Pack 4t5h34
November 2019 49
Aqa Gcse Biology- Cloning 4q4bi
October 2019 67
Space Hulk Campaigns 6r4x29
December 2019 267
Blood Bowl Magazine 01 6c4x2w
December 2019 71