Project management methodologies
Agile
This uses an iterative approach to delivering a project
throughout its entire life cycle. This means that this is a very adaptable
methodology and it has multiple frame works that can be used and the one that
is selected depends on
- Size
of organisation
- Structure
of team
- Resource
availability
- Stakeholder
requirements
Each of these frame works have their own pros and cons,
which means that although it may work for one team it may not work for another
team as effectively.
Types of frame works
Scrum - Scrum is an Agile framework used to manage
complex projects. It involves:
Roles:
- Product
Owner: Manages the product backlog and ensures value delivery.
- Scrum
Master: Facilitates the process and removes obstacles.
- Development
Team: Delivers the product increment in a self-organizing manner.
Artifacts:
- Product
Backlog: List of all potential product requirements.
- Sprint
Backlog: Items selected for the current sprint.
- Increment:
The usable product result from the sprint.
Events:
- Sprint:
Time-boxed work period (2-4 weeks) to create an increment.
- Sprint
Planning: Meeting to plan what will be done in the sprint.
- Daily
Scrum: Short daily meeting to sync up and plan daily work.
- Sprint
Review: Meeting to inspect the increment and adjust the backlog.
- Sprint
Retrospective: Meeting to reflect on the sprint and improve processes.
Scrum emphasizes iterative progress, team collaboration, and
continuous improvement.
Kanban - This framework is focused on visualizing and
managing work as it progresses through a system. Here’s a summary:
- Visual
Board: Uses a visual board (Kanban board) with columns representing
different stages of work (e.g., To Do, In Progress, Done). Tasks are
represented by cards that move through these columns.
- Work-in-Progress
(WIP) Limits: Sets limits on the number of tasks allowed in each stage to
prevent bottlenecks and ensure smooth flow.
- Continuous
Delivery: Emphasizes continuous delivery of work rather than working in
time-boxed iterations. Tasks are completed and delivered as soon as
they’re ready.
- Flow
Management: Focuses on optimizing the flow of work through the system,
identifying and addressing process inefficiencies.
- Feedback
and Improvement: Encourages regular feedback and incremental improvements
to the process.
Kanban is flexible and helps teams improve efficiency by
visualizing work, managing flow, and limiting work-in-progress.
Lean – This is aimed at maximizing value
and minimizing waste in processes. Here’s a summary:
- Value
Focus: Identifies and prioritizes what is valuable to the customer and
eliminates anything that does not add value.
- Waste
Reduction: Strives to remove waste (unnecessary activities, delays,
or resource usage) to improve efficiency and productivity.
- Continuous
Improvement: Encourages ongoing, incremental improvements to processes and
practices through feedback and reflection.
- Respect
for People: Values the input and well-being of all team members, fostering
a collaborative and empowered work environment.
- Flow
Optimization: Seeks to streamline work processes and ensure smooth,
efficient flow from start to finish.
Lean principles help teams deliver high-quality results more
efficiently by focusing on value, reducing waste, and continuously improving
processes.
Sprints - Sprints are a key component of the
Scrum framework within Agile. Here’s a summary:
- Time-Boxed
Iterations: Sprints are fixed-duration periods (typically 2-4 weeks)
during which a specific set of work is completed.
- Sprint
Planning: At the start of each sprint, a planning meeting is held to
define the sprint goal and select backlog items to work on.
- Work
Execution: The development team works on the selected items throughout the
sprint, aiming to complete them by the end of the period.
- Daily
Scrum: A short, daily meeting where the team discusses progress, plans the
day’s work, and identifies any obstacles.
- Sprint
Review: At the end of the sprint, a review meeting is held to demonstrate
the completed work and gather feedback.
- Sprint
Retrospective: A meeting held after the review to reflect on the sprint
process, discuss what went well, what didn’t, and identify improvements
for the next sprint.
Sprints provide a structured way to deliver incremental
value and continuously improve processes through regular cycles of planning,
execution, and reflection.
Waterfall
This is one of the most original project management
methodologies, so this means that the first needs to be complete before moving
onto the next part. It’s a very rigid structured approach for project
management so this has the factor of the associated risks. Is suitable for
smaller scale or simple projects but it would be useless to use as a part of a
large-scale project as these have dynamics that cannot be fully controlled.
Comments
Post a Comment