Skip to main content

Project management methodologies

 

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

Popular posts from this blog

Types of network adapters in virtual box

  Types of network adapters in VirtualBox In VirtualBox there’s multiple types of network adapters that can be used to configure virtual machines for different networking needs. Down below will give you a brief overview of each type. NAT (network address translation) The VM is placed behind a VirtualBox-managed router. This allows the VM to access the external network via the networks host’s IP, but the VM itself remains invisible to the outside. Its most suitable for simple internet access with minimal configuration NAT network This is like NAT, but it allows multiple VM’s to communicate with each other in the same NAT network all while sharing the host’s internet connection. Its commonly used when you want to simulate a small, isolated network of VM’s that can also access the internet. Bridged adapter This VM is connected directly to the physical network as if it is a separate device, it also receives its own IP address from the same network as the host. This is ide...

API's

  API's Types of API's REST API - Representational State Transfer is a commonly used API category that isn’t dependent on a specific protocol. It’s considered a relatively user-friendly API to work with and many developers are experienced in this technology. It’s an architecture style of communicating interfaces. SOAP API - Simple Object Access Protocol is an API that connects different platforms together through HTTP and XML. Its relatively older than other API implementations, but it provides more security as it follows strict protocols. It’s a protocol for communication between applications. ASP.NET API - Specific form of REST API developed around .NET technology. REST vs SOAP Both have some similarities for instance they both support SSL/TLS for secure and encrypted communications, also they both use HTTP to exchange information. When deciding which API to use you must take in many factors into consideration like, security, ACID compliance, and overall application design. F...
  Designing a SOHO network with DHCP Network requirements for the office Sales department – 4 computers Finance department – 3 computers Networking devices requirement: ·          1 router ·          2 switches (one for each department) ·          1 DHCP server Documentation I started by setting up the network topology and used the automatic connecting cable to connect all the devices together. Then I configured the server with IPv4 address and a subnet mask. to do this you have to press on the server and then go to desktop. Then I filled in all the parameters as seen below. Then I had to configure the DHCP server. To do this I clicked on the server > services > DHCP. Then I turned on the serves and configured the server as seen in this screenshot. For the next step I configured the router with the IPv4 address and subnet mask. To a...