Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Develop Requirements-based
Workflows and Deliverables …
Build scope definition and solutions - Elicit, Capture, and
Collec...
A working model using mission-driven measures in a team approach enables focus
on effective solutions
Course Goals
• Elicit, Capture, and Collect requirements needed to describe and support
scope of each deliverable
• Create...
Target Audience
Who should take this course?
• Subject Matter Experts (SMEs)
• Product Owners and Sponsors
• Business Proc...
Course Prerequisites
• Some technical experience
• Ability to collaborate and listen
• Capability to capture and define bu...
Develop Requirements-based
WBS, Workflows, and
Deliverables …
Section 1 Goal …
Build scope definition and solutions - Elic...
Welcome
What is Workflow (Process) Mapping and Work-
breakdown-Structure (WBS)
• A workflow model defines a
repeatable pattern of ...
• A workflow model defines a
repeatable pattern of sequenced
operations used to transform input
concepts or objects into i...
• Company’s Business Systems
Delivery
• Team Support of Product & Services
for Customers
• Undocumented Processes &
Proced...
Related Quotes
• Learn from yesterday, live for today, hope for
tomorrow. The important thing is not to stop
questioning. ...
Why are Workflow (Process) Mappings and
Work-breakdown-Structures (WBS) Needed?
• Why Workflow (process) Mapping is Import...
What’s This Course About?
• Learn skills and knowledge needed for
effective and development requirements-base
workflows an...
What you get from this course?
• Create the Business Requirements Document to support Scope and
Support for Deliverables
•...
What are course requirements?
• Some technical experience desired.
• Ability to collaborate and listen for business wants ...
Target Audience
Who should take this course?
• Subject Matter Experts (SMEs)
• Product Owners and Sponsors
• Business Proc...
Overview of Requirements-based WBS,
Workflows, and Deliverables
Section 2 Goals …
• Create Business Requirements Document ...
Product, Portfolio, Program, Project, Scope,
Deliverables, Workflow and WBS
Workflow (Process) Mapping
Workflow Process Ma...
Systems, Processes, Organizations, and Workflows –
Work, Knowledge and Information
System Environment
Systems, Processes, Organizations, and Workflows –
Work, Knowledge and Information
System-Architecture
Work (Activity-Base...
Business Solutions Lifecycle
Business Solutions Lifecycle
Business Solutions Lifecycle
WIPSDLC
Business Solutions Lifecycle
Business Solutions Lifecycle (BSL)
• Business Process and Systems Delivery
Management
• Requi...
What is Workflow (Process) Mapping and Work-
breakdown-Structure (WBS)
Workflow Model
What is Workflow (Process) Mapping and Work-
breakdown-Structure (WBS)
Product/Project WBS Model
What Is Workflow (Process...
Role of Workflow Mapping in Scope Baseline,
Deliverables and Scope Change Control
Role of WBS in Scope Baseline, Deliverables and
Scope Change Control?
Product Project Scope Measures
Role of WBS in Scope Baseline, Deliverables and
Scope Change Control?
WBS/Project
Scope Baseline
Scope Baseline
Creation P...
Role of WBS in Scope Baseline, Deliverables and
Scope Change Control?
Workflow & WBS Change Process
Fundamentals – Functional Decomposition and Object Oriented
Analysis for Workflows and WBS Mapping
Workflow Model Techniqu...
Fundamentals – Functional Decomposition and Object Oriented
Analysis for Workflows and WBS Mapping
OO Workflow Model Notat...
Fundamentals – Functional Decomposition and Object Oriented
Analysis for Workflows and WBS Mapping
UML Model Notation Work...
Project Requirements Impact on WBS
Requirements Traceability Matrix
Project Requirements Impact on Deliverables
Scope Key Components
Scope Planning
Knowledge Framework for Requirements-based Workflows,
WBS, and Deliverables Modeling Development
Information Vector
Knowle...
Knowledge Framework for Requirements-based Workflows,
WBS, and Deliverables Modeling Development
Formal Tacit Knowledge
Or...
Knowledge Framework for Requirements-based Workflows,
WBS, and Deliverables Modeling Development
Locus of Information
Work...
Knowledge Framework for Requirements-based Workflows,
WBS, and Deliverables Modeling Development
Flow Synchronization Effe...
What Are the Workflow and WBS Levels, ID, and
Numbering?
WBS Construction
WBS Construction
Workflow and WBS Levels, ID, an...
What Is a Workflow and WBS Component and
Type
Component Diagram
What Is a Workflow and WBS Work-Package
Package Diagram
Difference Between Workflow and WBS Schedule
Project Schedule Integration
Linking Workflow & WBS with Costs
Workflow & WBS Costs
Linking Workflow and WBS with Resources
Resource Breakdown Structure
Section 3: Integrating Workflow and WBS with
Communications, Risks,
Acquisitions, Human Resources, and Quality
Goals:
• El...
Using Workflow & WBS in Communications
RACI Matrix
• Responsible (R)
• Accountable (A)
• Consulted (C)
• Informed (I)
Using Workflow & WBS in Risk Management
Risk Management
Using Workflow & WBS in Quality Management …
Define Measure Analyze Improve ControlPlan-Do-Check-Act
Role of Agile, Waterfall, PMO, and PMBOK …
Agile Development
PMBOK
Prepare one Workflow Map and one WBS
Exercises –
Choose an exercise from any or all below or make up your own …
• Prepare ...
Conclusion …
• Section 4 – Develop Requirements-based WBS,
Workflows, and Deliverables – Conclusion
Conclusion …
Congratulations!! You’ve made it … You’ve Completed the Course Goals …
Course Goals …
• Elicit, Capture, and ...
Glossary
For definitions of terms used in this course, please see
downloadable Glossary below …
For Further Reading …
OO UML developed by “The 3 Amigos” Grady Booch, Ivar
Jacobson and James Rumbaugh at Rational Softwar...
Workflow & WBS: Develop Requirements-based Deliverables
Workflow & WBS: Develop Requirements-based Deliverables
Upcoming SlideShare
Loading in …5
×

Workflow & WBS: Develop Requirements-based Deliverables

2,220 views

Published on

What you get from this Course?
Upon successful completion you will ...
• Create the Business Requirements Document to support Scope and Support for Deliverables
• Use Structured Analysis to decompose deliverables into required Deliverables, Functions, Rules, Resources, Effort, Costs
• Elicit, Capture, and Collect requirements needed to describe and support scope of each deliverable
• Communicate with technical team using object-oriented analysis models
• Communicate with stakeholders using simplified object-oriented analysis models to clarify requirements
• Identify key relationships and activities for tasks and timing based on risks and issues derived from the project Work-breakdown-structure (WBS)
Completion of course goals enables skills an knowledge needed for identifying, assigning, tracking, controlling, and managing activities based on WBS and Workflow Modeling methods.
Skills and knowledge from this course aids capture & development of WBS and Workflow for effective portfolio/program/project delivery meeting scope, effort, risk, budgeting and scheduling requirements for your organization.
To achieve our course goals, the course is delivered using sections, lectures, quizzes, out-of-class exercises, and downloads. Also included with your course is a glossary and further reading references. As each section is presented, the section’s goals will be discussed and related lectures introduced.
During lectures, key concepts will be first presented then demonstrated as appropriate. Students are encouraged to use skills and knowledge discussed and demonstrated outside of class in their own work as much as possible to enhance learning success. During course lectures or outside lectures, students are further encouraged to ask questions or make comments and suggestions using Udemy’s Instructor Messaging service to contact me so I may do related research then get back to the student promptly with results.

Thank You & Best Regards,
Chuck Morrison, MBA, PMP

Published in: Business
  • Be the first to comment

Workflow & WBS: Develop Requirements-based Deliverables

  1. 1. Develop Requirements-based Workflows and Deliverables … Build scope definition and solutions - Elicit, Capture, and Collect Requirements, Rules, Deliverables, Resources. Chuck Morrison, MBA, PMP, CPIM, WWISA
  2. 2. A working model using mission-driven measures in a team approach enables focus on effective solutions
  3. 3. Course Goals • Elicit, Capture, and Collect requirements needed to describe and support scope of each deliverable • Create the Business Requirements Document to support Scope and Support for Deliverables • Use Structured Analysis to decompose deliverables into required Deliverables, Functions, Rules, Resources, Effort, Costs • Communicate with technical team using object-oriented analysis models • Communicate with stakeholders using simplified object-oriented analysis models to clarify requirements • Identify key relationships and activities for tasks and timing based on risks and issues derived from the project Work-breakdown-structure (WBS)
  4. 4. Target Audience Who should take this course? • Subject Matter Experts (SMEs) • Product Owners and Sponsors • Business Process Managers • Business Process Users • Product, Project, Portfolio, and Program Managers • Quality Assurance • Business Analysts & Architects • System & Software Developers
  5. 5. Course Prerequisites • Some technical experience • Ability to collaborate and listen • Capability to capture and define business and technical requirements • Interest in business analysis and information architecture • Ability to collect and organize tasks, activities and resources into diagrams and graphical models
  6. 6. Develop Requirements-based WBS, Workflows, and Deliverables … Section 1 Goal … Build scope definition and solutions - Elicit, Capture, and Collect Requirements, Rules, Deliverables, Resources..
  7. 7. Welcome
  8. 8. What is Workflow (Process) Mapping and Work- breakdown-Structure (WBS) • A workflow model defines a repeatable pattern of sequenced operations used to transform input concepts or objects into intended output concepts or objects. • A work breakdown structure (WBS) is used to effectively decompose project scope , to improve estimating, to better control project execution execution and to more accurately verify project required deliverables for product, portfolio, program, and project completion Workflow (Process) Mapping
  9. 9. • A workflow model defines a repeatable pattern of sequenced operations used to transform input concepts or objects into intended output concepts or objects. • A work breakdown structure (WBS) is used to effectively decompose project scope , to improve estimating, to better control project execution execution and to more accurately verify project required deliverables for product, portfolio, program, and project completion What is Workflow (Process) Mapping and Work- breakdown-Structure (WBS) Model Driven Architecture
  10. 10. • Company’s Business Systems Delivery • Team Support of Product & Services for Customers • Undocumented Processes & Procedures • Impact on Time or Resources of Security & Safety • What to Do … Next Steps … Imagine …
  11. 11. Related Quotes • Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. – Albert Einstein • Continuous improvement is not about the things you do well — that’s work. Continuous improvement is about removing the things that get in the way of your work. The headaches, the things that slow you down, that’s what continuous improvement is all about. ~Bruce Hamilton • Perfection is not attainable, but if we chase perfection we can catch excellence. -Vince Lombardi • The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency. ~Bill Gates • What gets measured, gets managed. ~Peter Drucker
  12. 12. Why are Workflow (Process) Mappings and Work-breakdown-Structures (WBS) Needed? • Why Workflow (process) Mapping is Important – Five key considerations for workflow mapping – Workflow Process Mapping as a Learning Tool – Workflow Mapping Can Lead to Optimizing Efficiency • Why Work Breakdown Structure (WBS) is Important – Scope, Deliverables, Work Packages, Costs – Schedule, Functionality, Responsibility
  13. 13. What’s This Course About? • Learn skills and knowledge needed for effective and development requirements-base workflows and deliverables • Support valuable solutions for business and IT organizations • Use Workflow Models to manage how a process works and use Work-breakdown- Structure (WBS) structure
  14. 14. What you get from this course? • Create the Business Requirements Document to support Scope and Support for Deliverables • Use Structured Analysis to decompose deliverables into required Deliverables, Functions, Rules, Resources, Effort, Costs • Elicit, Capture, and Collect requirements needed to describe and support scope of each deliverable • Communicate with technical team using object-oriented analysis models • Communicate with stakeholders using simplified object-oriented analysis models to clarify requirements • Identify key relationships and activities for tasks and timing based on risks and issues derived from the project Work-breakdown-structure (WBS)
  15. 15. What are course requirements? • Some technical experience desired. • Ability to collaborate and listen for business wants and needs • Capability to capture and define business and technical requirements • Interest in the fields of business analysis and information architecture • Ability to collect and organize tasks, activities and resources into diagrams and graphical models
  16. 16. Target Audience Who should take this course? • Subject Matter Experts (SMEs) • Product Owners and Sponsors • Business Process Managers • Business Process Users • Product, Portfolio, Project, and Program Managers • Business Analysts & Architects • Quality Assurance • System & Software Developers
  17. 17. Overview of Requirements-based WBS, Workflows, and Deliverables Section 2 Goals … • Create Business Requirements Document to support Scope and Support for Deliverables • Use Structured Analysis to decompose deliverables into required Deliverables, Functions, Rules, Resources, Effort, Costs • Communicate with technical team using object-oriented analysis models
  18. 18. Product, Portfolio, Program, Project, Scope, Deliverables, Workflow and WBS Workflow (Process) Mapping Workflow Process Mapping Product, Portfolio, Program, Project Scope and Deliverables • Product Scope • Portfolio Scope • Program and Project Scope • Workflow Mappings and Work Breakdown Structures • Workflow Models – BPE, BPM, BPR, AI, OODA … • Processes • Planning and scheduling Work Breakdown Structure (WBS)
  19. 19. Systems, Processes, Organizations, and Workflows – Work, Knowledge and Information System Environment
  20. 20. Systems, Processes, Organizations, and Workflows – Work, Knowledge and Information System-Architecture Work (Activity-Based), Knowledge and Information Mapping • Systems • Processes • Organizations • Workflows • Work Breakdown Structure (WBS)
  21. 21. Business Solutions Lifecycle Business Solutions Lifecycle
  22. 22. Business Solutions Lifecycle WIPSDLC
  23. 23. Business Solutions Lifecycle Business Solutions Lifecycle (BSL) • Business Process and Systems Delivery Management • Requirements Definition & Management • Lifecycle Quality Management • Change Management • Continuous Process Improvement (CPI) • Workflow Modeling Lifecycle Work-in-Process System Development Lifecycle (WIPSDLC) • WIPSDLC Model Phase Tracks include Methodology Phases/Deliverables (SDLC) SDLC
  24. 24. What is Workflow (Process) Mapping and Work- breakdown-Structure (WBS) Workflow Model
  25. 25. What is Workflow (Process) Mapping and Work- breakdown-Structure (WBS) Product/Project WBS Model What Is Workflow (Process) Mapping? • Choose a process • process “As-Is” • Identify problems • Assign responsibilities • Create master plan (Scope, Deliverables) • Follow through What Is Work-breakdown-Structure (WBS) Work Breakdown Structure (WBA) Modeling Considerations
  26. 26. Role of Workflow Mapping in Scope Baseline, Deliverables and Scope Change Control
  27. 27. Role of WBS in Scope Baseline, Deliverables and Scope Change Control? Product Project Scope Measures
  28. 28. Role of WBS in Scope Baseline, Deliverables and Scope Change Control? WBS/Project Scope Baseline Scope Baseline Creation Process
  29. 29. Role of WBS in Scope Baseline, Deliverables and Scope Change Control? Workflow & WBS Change Process
  30. 30. Fundamentals – Functional Decomposition and Object Oriented Analysis for Workflows and WBS Mapping Workflow Model Techniques What Is Functional Decomposition? When and How is Is Functional Decomposition Used? • Object Oriented Methods • UML Diagrams How to Diagram a Workflow – • Identify a Process • Name the Process • Identify a Clear Process Start/End Conditions and Exceptions • Identify Workflow Diagram Purpose • List or Diagram All Steps Identified from Start to End of Process • Identify Exceptions and Rules for Each Process Step • Leverage Relevant UML Model Symbols and/or Workflow Modeling Symbol Set
  31. 31. Fundamentals – Functional Decomposition and Object Oriented Analysis for Workflows and WBS Mapping OO Workflow Model Notation What Is Functional Decomposition? When and How is Is Functional Decomposition Used? • Object Oriented Methods • UML Diagrams How to Diagram a Workflow – • Identify a Process • Name the Process • Identify a Clear Process Start/End Conditions and Exceptions • Identify Workflow Diagram Purpose • List or Diagram All Steps Identified from Start to End of Process • Identify Exceptions and Rules for Each Process Step • Leverage Relevant UML Model Symbols and/or Workflow Modeling Symbol Set
  32. 32. Fundamentals – Functional Decomposition and Object Oriented Analysis for Workflows and WBS Mapping UML Model Notation Workflow Modeling Symbol Set
  33. 33. Project Requirements Impact on WBS Requirements Traceability Matrix
  34. 34. Project Requirements Impact on Deliverables Scope Key Components Scope Planning
  35. 35. Knowledge Framework for Requirements-based Workflows, WBS, and Deliverables Modeling Development Information Vector Knowledge Universe
  36. 36. Knowledge Framework for Requirements-based Workflows, WBS, and Deliverables Modeling Development Formal Tacit Knowledge Organizational Functioning Locus Mode Action Interactions
  37. 37. Knowledge Framework for Requirements-based Workflows, WBS, and Deliverables Modeling Development Locus of Information Work Information Flow
  38. 38. Knowledge Framework for Requirements-based Workflows, WBS, and Deliverables Modeling Development Flow Synchronization Effects
  39. 39. What Are the Workflow and WBS Levels, ID, and Numbering? WBS Construction WBS Construction Workflow and WBS Levels, ID, and Numbering Work Breakdown Structure (WBS) Guidelines Workflow (Process) Mapping Process Model levels Two Levels of Workflow and WBS Component • Level of Effort • Discrete Workflow or WBS Component Workflow and WBS Fields an Attributes
  40. 40. What Is a Workflow and WBS Component and Type Component Diagram
  41. 41. What Is a Workflow and WBS Work-Package Package Diagram
  42. 42. Difference Between Workflow and WBS Schedule Project Schedule Integration
  43. 43. Linking Workflow & WBS with Costs Workflow & WBS Costs
  44. 44. Linking Workflow and WBS with Resources Resource Breakdown Structure
  45. 45. Section 3: Integrating Workflow and WBS with Communications, Risks, Acquisitions, Human Resources, and Quality Goals: • Elicit, Capture, and Collect requirements needed to describe and support scope of each deliverable • Create the Business Requirements Document to support Scope and Support for Deliverables • Use Structured Analysis to decompose deliverables into required Deliverables, Functions, Rules, Resources, Effort, Costs • Communicate with technical team using object-oriented analysis models • Communicate with stakeholders using simplified object-oriented analysis models to clarify requirement • Identify key relationships and activities for tasks and timing based on risks and issues derived from the project Work-breakdown-structure (WBS)
  46. 46. Using Workflow & WBS in Communications RACI Matrix • Responsible (R) • Accountable (A) • Consulted (C) • Informed (I)
  47. 47. Using Workflow & WBS in Risk Management Risk Management
  48. 48. Using Workflow & WBS in Quality Management … Define Measure Analyze Improve ControlPlan-Do-Check-Act
  49. 49. Role of Agile, Waterfall, PMO, and PMBOK … Agile Development PMBOK
  50. 50. Prepare one Workflow Map and one WBS Exercises – Choose an exercise from any or all below or make up your own … • Prepare Workflow and WBS diagrams to make a pot of coffee • Prepare Workflow and WBS diagrams to mow the lawn • Prepare Workflow and WBS diagrams to make a shopping list then go shopping • Prepare to periodically review customer credit accounts • Prepare a product bill-of-materials and assembly workflow process
  51. 51. Conclusion … • Section 4 – Develop Requirements-based WBS, Workflows, and Deliverables – Conclusion
  52. 52. Conclusion … Congratulations!! You’ve made it … You’ve Completed the Course Goals … Course Goals … • Elicit, Capture, and Collect requirements needed to describe and support scope of each deliverable • Create the Business Requirements Document to support Scope and Support for Deliverables • Use Structured Analysis to decompose deliverables into required Deliverables, Functions, Rules, Resources, Effort, Costs • Communicate with technical team using object-oriented analysis models • Communicate with stakeholders using simplified object-oriented analysis models to clarify requirement • Identify key relationships and activities for tasks and timing based on risks and issues derived from the project Work-breakdown-structure (WBS)
  53. 53. Glossary For definitions of terms used in this course, please see downloadable Glossary below …
  54. 54. For Further Reading … OO UML developed by “The 3 Amigos” Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software during 1994–95 with further development led by them through 1996 … Rational Software transferred to IBM … OO UML accepted by OMG & ISO Please see other References (attached) ...

×