The Details Behind Project Workflow Management | Episode 317

About this Video

• Video Title: The Details Behind Project Workflow Management | Episode 317
• Channel: CorneliusFichtner
• Speakers: Cornelius Fichtner, Dan Epstein, Rich Maltzman
• Duration: 35:11

Introduction

This podcast episode delves into project workflow management, expanding on a previous discussion with Dan Epstein and Rich Maltzman. The hosts explore Dr. Harold Kerzner's perspective on the method, comparing it to traditional methodologies and outlining its practical applications and workflow.

Key Takeaways

• Project Workflow Management's Value: Project workflow management prevents project problems and builds quality into the end product, offering a more valuable alternative to complex methodologies. It leads to increased project success rates and improved team morale.
• The Four-Frame Framework: The framework consists of four frames: Requirements, Planning/High-Level Design, Construction, and Closing. Each frame contains multiple processes, executed iteratively and concurrently, unlike sequential traditional methods.
• Frame Breakdown:
  • Requirements Frame: Establishes project justification, allocates requirements, secures funding, and produces a Business Requirements Traceability Matrix and Business Requirements Document.
  • Planning/High-Level Design Frame: Develops a detailed plan, addresses change requests, provides estimates, and plans for risk containment and scope changes. It provides more practical, step-by-step guidance than traditional methodologies.
  • Construction Frame: Focuses on developing and implementing the business solution, managing change requests, and simultaneously monitoring risks, costs, schedule, and quality. Includes processes for troubled project assessment and corrective action.
  • Closing Frame: Verifies solution alignment with project goals, includes user acceptance testing, user training, resource release, and ensures product sustainability.
• Simultaneous Monitoring and Control: The Construction frame emphasizes simultaneous monitoring and management of risks, costs, schedule, and quality, adapting frequently based on project needs and challenges. A "troubled project assessment" process is used to identify and address issues.
• Implementation Strategy: Successful implementation requires a top-down approach, starting with pilot projects and training, addressing inherent resistance to change.