*Quick recap*

The meeting focused on project management concepts, particularly scope

management and scheduling techniques. Bala led a detailed discussion on the
*19 planning components* and the creation of a *Project Management Plan
(PMP), which integrates 10 management plans and nine other components* . The
importance of collecting complete requirements and using tools like *affinity
diagrams and mind mapping* was emphasized. Bala explained the role of the
*business analyst in adaptive environments* and the use of *Requirement
Traceability Matrix (RTM) in traditional projects.* The meeting also covered the
creation of *Work Breakdown Structure (WBS), the concept of rolling wave
planning* , and the *significance of buy-in from stakeholders.* Various scheduling
methodologies, including *Critical Path Method (CPM) and Critical Chain Project
Management (CCPM)* , were discussed. The session concluded with questions
and answers about project management practices and scenarios.

*Summary*

*Project Management Plan Components*

Bala discussed the importance of collecting and managing various planning

components to create a living document called the Project Management Plan
(PMP). He outlined the 10 management plans and nine additional components
that need to be integrated into the PMP. Bala emphasized the need for the
technical team, particularly the scope team, to follow *all six processes under the
scope management knowledge area without tailoring.* He also explained the role
of the requirement management plan and its importance in collecting detailed
requirements for the project. Bala highlighted the *significance of collecting
complete requirements from stakeholders to ensure project success and achieve
business objectives.*

*Requirement Gathering Tools Overview*

Bala discussed various tools and techniques used in requirement gathering and
project management, including brainstorming, *nominal group technique (NGT),
affinity diagrams, mind mapping, Joint Application Design (JAD), Quality Function
Deployment (QFD), House of Quality (HOQ), prototypes* , and *Requirement
Traceability Matrix (RTM).* He explained the use of these tools in both traditional
and adaptive project environments, emphasizing their *relevance to collecting,
categorizing, and tracking requirements effectively* . Bala also highlighted the
importance of creating clear, concise, measurable, and testable requirements
and shared examples of how *RTM can be used to track requirements from the
initial stage to the deliverable stage.*

*Traditional vs Adaptive Project Management*

Bala discussed the differences between traditional and adaptive project

management, emphasizing that while *traditional projects require a detailed
scope statement and documentation, adaptive projects allow for more flexibility
with requirements collected and prioritized by the product owner.* He explained
that in adaptive environments, the Definition of Done is used for individual
features during iteration reviews, while in traditional projects, acceptance criteria
are defined at a larger scope. Bala also covered the concept of design-build
projects and the importance of having an approved scope statement, which
includes *detailed descriptions of deliverables, assumptions, constraints,
boundaries, and acceptance criteria* . He concluded by highlighting the roles of
project managers and t *eam leaders in ensuring CLEAR goals,* collaboration,
and the use of the *SMART principle for scope management.*

*User Story Refinement and Decomposition*

Bala discussed the importance of refining user stories through backlog grooming
sessions, which involve the product owner and typically take 1-2 hours per week.
He explained the concepts of epics and user stories, using an example of an
online flight booking system, and described how larger epics are broken into
smaller features. Bala also *covered the work breakdown structure (WBS) and
decomposition, explaining that both are tools for breaking down large projects
into manageable components* , with WBS being a document and decomposition
being a technique. He emphasized the *100% rule* , where team members must
contribute exactly 100% to their assigned work, and introduced the *concept of
Code of Accounts,* which involves assigning numerical or alphanumeric IDs to
WBS components to facilitate resource allocation and project tracking.
*Work Breakdown Structure Fundamentals*

Bala discussed the importance of the *Work Breakdown Structure (WBS)* in

project management, emphasizing its role in decomposing larger project scopes
into manageable components called work packages. He explained that *WBS
components are deliverable-focused rather than task or customer-focused,* and
he clarified the hierarchy of WBS documents, including the *WBS dictionary for
detailed technical information* . Bala also covered the *concept of rolling wave
planning* , which *involves progressive elaboration to plan near-term work in
detail while keeping far-term work at a milestone level* . He stressed the need
for the technical team to establish the scope baseline and the importance of
getting stakeholder buy-in. Bala concluded by mentioning the control account for
reporting cost status and the *100% rule for ensuring complete project
coverage.*

*Project Management Decomposition and WBS*

Bala discussed *decomposition and Work Breakdown Structure (WBS)* in project

management, explaining how work can be broken down into smaller components
and how WBS is structured differently in traditional and adaptive project
management. He covered the *scope baseline* , explaining that once a contract
is awarded, a copy goes to the client and no changes can be made without
following the change management plan and configuration management plan.
Bala also explained the concept *of effort measurement in project scheduling,
distinguishing between level of effort, discrete effort, and apportioned effort, and
discussed the units of measure used by planning and commercial teams to track
performance.*

*International Calendar and Project Scheduling*

Bala discussed the importance of understanding and converting different

calendar systems for international projects, emphasizing the need to align with
local and global calendars. He explained the concept of the *critical path method
(CPM)* and its application in project scheduling, including the calculation of float
and its significance in project management. Bala also introduced the concept of
the *Critical Chain Project Management (CCPM) methodology* as an alternative
to traditional scheduling methods, highlighting its potential benefits.

*Project Management Scenarios and Solutions*

The meeting focused on discussing various project management scenarios and

their solutions. Bala and Naja debated the correct answers to several questions,
with *Bala emphasizing the importance of understanding stakeholder
communication needs* and Ali explaining why the agile approach requires more
frequent SME involvement. The group also discussed how to handle a team
member's resignation, with Bala advocating for *developing a mitigation strategy
before the resignation* is presented to functional managers.

*Project Management Decision-Making Scenarios*

The meeting focused on project management scenarios and decision-making.

Bala discussed the importance of assessing business benefits before
implementing a sponsor's recommendation to co-locate team members, even
when it involves additional costs. They also *addressed organizational audit
policies, emphasizing the need for project managers to set clear policies and
communicate them effectively.* The discussion concluded with scenarios about
managing team disruptions and handling disagreements between product
owners and development teams over project timelines, with Bala advocating for
coaching and clear communication as solutions.

*Work Breakdown Structure (WBS)*

A *WBS* is a general project management tool that involves a hierarchical

decomposition of a project's total scope into smaller, more manageable
deliverables or work packages.

*Purpose* : To define, organize, and visualize the entire scope of work required to
achieve project objectives. It is deliverable-oriented and ensures that 100% of
the project scope is captured.

*Methodology:* It can be used in traditional (Waterfall) project management to

plan the entire project upfront, or adapted for Agile use.
*Structure* : It breaks down the main project goal into major deliverables, which
are further subdivided into sub-deliverables and eventually into "work packages"
(the lowest level of detail).

*Outcome* : It provides a clear framework for estimating costs, assigning

responsibilities, setting schedules, and tracking progress.

*Epics in Agile Project Management*

In an Agile context (like *Scrum or Kanban* ), *an epic is a large body of work or
a high-level requirement/feature that cannot be completed in a single iteration
(sprint).*

*Purpose* : To serve as a placeholder for large requirements and to group

related, smaller work items (user stories/tasks) that drive toward a common goal
or improved functionality.

*Methodology:* Epics are refined and broken down into smaller user stories
incrementally as the project progresses and more is learned. They are prioritized
in the product backlog and typically span multiple sprints or teams.

*Outcome* : Epics are an organizational tool to track progress towards larger

goals, but unlike a WBS's work packages, they are not specific deliverables to be
completed by a fixed date upfront; their scope can evolve
The House of Quality (HoQ ) is a conceptual planning matrix used in Quality
Function Deployment (QFD ) to translate customer requirements into concrete
product design and engineering specifications. Its name derives from its physical
structure, which resembles a house with a roof, walls, and a basement.

Core Components ("The Rooms")

• The Left Wall (Customer Requirements) : Lists the "Whats"—the specific
needs, wants, and expectations gathered directly from the Voice of the Customer
(VOC).

• The Ceiling (Design Requirements): Lists the "Hows"—the technical or

engineering characteristics that will satisfy the customer needs.

• The Main Room (Relationship Matrix ): The central grid where teams use
symbols or scores (often 9 for strong, 3 for moderate, 1 for weak) to show how
strongly each design requirement affects each customer need.
• The Roof (Correlation Matrix) : A triangular matrix that identifies how
design requirements interact with one anot

her, highlighting trade-offs (e.g., increasing engine power mi

A breadboard is a reusable, solderless platform used to build and test electronic

circuit prototypes by inserting components and wires into interconnected holes.
It's ideal for quick experimentation because it allows for easy modification
without soldering, though it is intended for temporary prototypes, not permanent
circuits.