Module 2
Sports project management
Planning Stage of Project Management
• Definition: Detailed planning to define project scope, goals, timelines,
budget, and resources.
1Define Project Scope
2Develop Project Schedule
3Determine Budget
4Assign Resources
5develop risk and mitigation
6communication activity
7 quality assurance
Project scope management in detail
• Gather Requirements:
• Identify Project Objectives:
• Define Deliverables:
• Establish Boundaries:
• Document Scope Statement:
Project schedule
• Definition: A timeline of tasks, milestones, and deadlines that
outlines the project scope, duration, and resource allocation.
Components of Project Schedule:
1 . Work Breakdown Structure (WBS): Hierarchical decomposition of project
scope into manageable tasks
.2. Task List: Detailed list of tasks with estimated durations, dependencies,
and resource assignments.
3. Milestones: Significant events or accomplishments marking project
progress
.4. Deadline Schedule: Timeline of tasks with start and end dates, including
milestones and deliverables.
5. Resource Allocation: Assignment of resources (team members, equipment,
materials) to tasks.
QUALITY ASSURANCE
Definition:Systematic process to ensure product/service meets
required quality standards, specifications, and customer expectations.
QA Objectives:
1. Defect Prevention: Identify and prevent defects early in
development.
2. Quality Improvement: Continuously monitor and improve processes
and products.
3. Customer Satisfaction: Ensure products/services meet customer
needs and expectations
.4. Compliance: Verify adherence to regulatory requirements,
standards, and specifications.
Benefits of quality assurance
• Reduced defects and variations
• Improved quality and customer satisfaction
• Increased efficiency and productivity
• Enhanced data-driven decision making
• Significant cost savings
Scope creep
• Definition: Uncontrolled growth or change in project scope, often resulting
in additional work, cost overruns, and schedule delays.
• Causes of Scope Creep:
• Poor Requirements Gathering: Insufficient understanding of project needs.
• Lack of Clear Goals: Unclear or changing project objectives.
• Inadequate Change Control: Failing to manage and approve changes
properly.
• Stakeholder Interference: Unapproved changes requested by stakeholders.
• Team Misunderstandings: Miscommunication among team members about
scope.
REASONS OF SCOPE CREEP
• Increasing Task List: New tasks appear without approval.
• Blurred Boundaries: Scope boundaries become unclear.
• Unbudgeted Work: Work done without allocated budget.
• Schedule Slippage: Project timeline extends beyond original estimate.
• Team Overload: Team members overwhelmed with excessive
workload
PREVENTING SCOPE CREEP
• Clear Requirements Gathering
• Well-Defined Scope Statement
• Change Control Process
• Regular Scope Reviews
• Stakeholder Management
What is a RACI Matrix
• A RACI matrix is a tool in project management designed to clarify team
roles and responsibilities across tasks.
• Each role is categorized as Responsible, Accountable, Consulted, or
Informed, ensuring that everyone understands their role in a project’s
success. By assigning these roles, project managers prevent confusion and
overlapping duties while increasing accountability.
• The RACI framework is especially beneficial for complex projects where
clear role distribution is essential for smooth workflows and improved
communication.
Components of RACI matrix
Responsible
The individual(s) with responsibility for the task or deliverable is
responsible for developing and completing the project deliverables
themselves. The responsible parties are typically hands-on team
members who make direct contributions toward the completion of
the project. The responsible team is composed of the project’s
doers, who work hands-on to ensure that each deliverable is
completed.
Some examples of responsible parties are
• Project managers
• Business analysts
• Developers
• Graphic designers
• Copywriters
• One risk when using a RACI matrix is unintentionally overloading a single team member
with too many responsibilities. If one person is designated as Responsible for too many
tasks, they may struggle to manage their workload, leading to delays or burnout. To avoid
this, project managers should carefully distribute responsibilities across the team and
ensure that no individual is overwhelmed. Regularly reviewing the matrix throughout the
project helps identify and address any imbalances before they become critical.
Accountable
• Accountable parties ensure accountability to project deadlines, and
ultimately, accountability to project completion. This group
frequently also falls under the informed category.
Some examples of accountable parties are:
• Product owners
• Signature authorities
• Business owners
Accountable
• By clearly defining roles, a RACI matrix prevents decision-making bottlenecks
and confusion in the approval process.
• When roles are ambiguous, critical decisions can get delayed, as team
members might not know who holds final accountability.
• The RACI model eliminates this issue by ensuring that the individual
responsible for approvals is clearly designated as Accountable.
• Additionally, identifying who needs to be consulted or informed reduces
unnecessary back-and-forth, allowing decisions to be made quickly and
efficiently without roadblocks.
• This clear communication flow optimizes project progression and prevents
delays.
Consulted
Consulted individuals’ opinions are crucial, and their feedback needs to be
considered at every step of the game. These individuals provide guidance
that is often a prerequisite to other project tasks, for example, providing legal
guidance on a project throughout the process. If you are working on new
product development or expansion, this could essentially be the entire
organization.
Informed
• Informed persons are those that need to stay in the loop of
communication throughout the project. These individuals do not
have to be consulted or be a part of the decision-making, but they
should be made aware of all project updates. Typically, this party
consists of business owners or stakeholders that are more interested
in viewing the project at a 30,000-foot view. Keep this group on your
CC list for awareness of topics, decisions, and progress — that
includes making them part of the initial project kickoff and project
demos as optional attendees.
Example RACI
GANTT CHART
• A gantt chart is a horizontal bar chart used in project management to
visually represent a project over time. Gantt charts typically show
you the timeline and status—as well as who’s responsible—for each
task in the project.
• In project management, gantt charts are used to schedule, track, and
communicate deliverables, deadlines, dependencies, and resource
assignments. They’re particularly helpful in managing complex
projects with interdependencies that a simple to-do list or Kanban
board can’t handle.
PURPOSE OF GANTT CHART
A gantt chart allows you to simplify complex projects into an easy-to-follow
plan that includes:
• How a project breaks down into tasks
• When each task will begin and end
• How long each task will take
• Who’s assigned to each task
• How tasks relate to and depend on each other
• When important meetings, approvals, or deadlines need to happen
• How work is progressing in a project
• The full project schedule from start to finish
COMPONENTS OF GANNT CHART
• Task list: Runs vertically down the left of the gantt chart to describe project work and may
be organized into groups and subgroups
• Timeline: Runs horizontally across the top of the gantt chart and shows months, weeks,
days, and years
• Dateline: A vertical line that highlights the current date on the gantt chart
• Bars: Horizontal markers on the right side of the gantt chart that represent tasks and
show progress, duration, and start and end dates
• Milestones: Yellow diamonds that call out major events, dates, decisions, and deliverables
• Dependencies: Light gray lines that connect tasks that need to happen in a certain order
• Progress: Shows how far along work is and may be indicated by percent complete and/or
bar shading
• Resource assigned: Indicates the person or team responsible for completing a task