workflow & wbs: develop requirements-based deliverables

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

A working model using mission-driven measures in a team approach enables focus on effective solutions

Develop Requirements-based Workflows and Deliverables

https://www.facebook.com/

https://www.youtube.com/

http://accounts.google.com/

https://twitter.com/?lang=en

https://www.linkedin.com/uas/login

http://www.pmi.org/

http://www.chuckmorrison.com/

https://www.udemy.com/courses/

WORKFLOW MODELSONLINE

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)

Target AudienceWho 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

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

Develop Requirements-based WBS, Workflows, and Deliverables …

Section 1 Goal …Build scope definition and solutions - Elicit, Capture, and Collect Requirements, Rules, Deliverables, Resources..

Welcome

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

• 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


Model Driven Architecture

• 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 …

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

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

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

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)

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

Target AudienceWho 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

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

Product, Portfolio, Program, Project, Scope, Deliverables, Workflow and WBS


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)

Systems, Processes, Organizations, and Workflows – Work, Knowledge and Information

System Environment

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)

Business Solutions Lifecycle



WIPSDLC

Business Solutions LifecycleBusiness 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


Workflow Model


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

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


WBS/Project Scope Baseline

Scope Baseline Creation Process


Workflow & WBS Change Process

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


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


UML Model Notation Workflow Modeling Symbol Set

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 VectorKnowledge Universe


Formal Tacit Knowledge Organizational Functioning Locus Mode Action Interactions


Locus of InformationWork Information Flow


Flow Synchronization Effects

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


Process Model levels

Two Levels of Workflow and WBS Component• Level of Effort • Discrete Workflow or WBS Component

Workflow and WBS Fields an Attributes

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: • 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)

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 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

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 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)

GlossaryFor 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 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) ...