workflow & wbs: develop requirements-based deliverables
TRANSCRIPT
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
Course Goals • 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)
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
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 … to my Udemy Training course Hello, I'm Chuck Morrison My specialties are: Business Process Engineering, Software Systems Development, Cross-Functional Program and Change Management. My significant skills and accomplishments include ... My significant accomplishments also include …
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 the project scope , to improve estimating, to better control the project execution execution and to more accurately verify project required deliverables ityity to product, portfolio, program, and project completion
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 the project scope , to improve estimating, to better control the project execution execution and to more accurately verify project required deliverables traceability to product, portfolio, program, and project completion
• Company’s Business Systems Delivery
• Team Support Product & Services for Customers
• Undocumented Processes & Procedure
• Impact on Time or Resources or 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 a 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 a 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 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
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
Systems, Processes, Organizations, and Workflows – Work, Knowledge and Information
Systems, Processes, Organizations, and Workflows – Work, Knowledge and Information
System-Architecture
Business Solutions Lifecycle
Business Solutions Lifecycle
Business Solutions Lifecycle
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
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 Process
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 Techniques
Fundamentals – Functional Decomposition and Object Oriented Analysis for Workflows and WBS Mapping
OO Workflow Model Notation
Fundamentals – Functional Decomposition and Object Oriented Analysis for Workflows and WBS Mapping
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 Vector Knowledge Universe
Knowledge Framework for Requirements-based Workflows, WBS, and Deliverables Modeling Development
Formal Tacit Knowledge Organizational Functioning Locus Mode Action Interactions
Knowledge Framework for Requirements-based Workflows, WBS, and Deliverables Modeling Development
Locus of Information Work Information Flow
Knowledge Framework for Requirements-based Workflows, WBS, and Deliverables Modeling Development
Flow Synchronization Effects
What Are the Workflow and WBS Levels, ID, and Numbering
WBS Construction
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
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
Using Workflow & WBS in Risk Management
Using Workflow & WBS in Procurement …
Role of Agile, Waterfall, PMO, and PMBOK …
Conclusion …
• Section 4 – Develop Requirements-based WBS, Workflows, and Deliverables – Conclusion
Conclusion … Congratulations!! You’ve made it … You’ve Completed the Course Goals … • Creation and maintenance of standards and methods • Understand Confidentiality, Integrity, and Availability (CIA) concepts and relationships • Overview key principles and objectives of CISSP domains • Apply concepts of safety and security to portfolio, program, and project management • Project Management consulting and mentoring on methodology, and dealing with security
and risk management • Apply safety and security concepts to assets, SDLC security, Communications &
Networks security • Understand apply concepts related to identity and access management • Understand apply concepts related to security assessment and testing and security
operations • Apply Personally Identifiable Information (PII), Payment Card Industry Data Security
Standard (DSS/PCI) concepts
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 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) ...