Iterative and Agile project management models and methodologies

PMBOK + UP

PMBOK is a framework that outlines the best practices and guidelines for project management, while the UP (Unified Process) is a software engineering process that provides a disciplined approach to the construction, development and maintenance of software. UP encourages many best practices and iterative and incremental development.

Here are some situations where PMBOK and UP can be used together:

1. Large-scale software development projects: PMBOK can be used to manage the overall project, while UP can be used to manage the software development process. UP provides a framework for iterative development, while PMBOK provides guidelines for managing scope, cost, quality, and risk.
2. Complex projects with multiple stakeholders: PMBOK can be used to manage the overall project, while UP can be used to manage the software development process. This approach can help to ensure that the software development process aligns with the overall project goals and objectives.
3. Projects with strict regulatory requirements: PMBOK can provide the framework for compliance and risk management, while UP can provide the software development process. This approach can help to ensure that the software development process is compliant with regulatory requirements.

An appropriate methodology for software development project management must provide the organization’s project managers with a perspective of the management model and methodologies. In this sense, UP is not sufficient, since it does not propose the following points in project management: human resources administration, procurement and contracting administration, cost administration, project scope administration, quantitative risk analysis and approach and location of resources for its treatment, among other techniques.

Instead, these techniques are addressed by the PMBOK, which has a framework for project management in which each area of knowledge is constantly evolving. In this sense, PMBOK expands the knowledge, techniques, skills and tools in order to execute projects in a more effective way.

From the point of view of management, the life cycle of the UP software is divided into 4 sequential phases, each of which ends with the fulfillment of a main objective. The UP development process is also broken down into 9 disciplines that acquire greater or lesser relevance depending on the phase of the project we are in.¹.

Output artifacts for each of the disciplines:

1.1.-Business modelling

• Domain model.

1.2.-Requirements

• Use case model.
• Vision
• Supplementary specification.
• Glossary.

1.3.-Analysis and design of systems

• Technical documentation.

1.4.-Development

1.5.-Testing

• Test Master Plan.

1.6.- Deployment

1.7.-Configuration and change management

• Change Management Plan

1.8.-Management

• Plan for project management.

1.9.-Technical Environment

• Architecture document

Business Modelling	Requirements gathering	Analysis and design	Development	Testing	Deployment	Configuration and change management	Management	Technical Environment
Domain model.	Use case model. Vision. Supplementary specification. Glossary.	Technical documentation.		Test Master Plan.		Change Management Plan	Plan for project management.	Architecture document

SCRUM

Scrum is an Agile software development methodology that is used to manage and complete complex projects. Here’s a brief summary of the Scrum framework:

1. Scrum Roles: There are three roles in Scrum: Product Owner, Scrum Master, and Development Team.
2. Product Backlog: The Product Owner maintains a prioritized list of user stories, which is called the Product Backlog.
3. Sprint Planning: At the beginning of each Sprint, the Development Team selects a set of user stories from the Product Backlog to work on. The team then breaks down each user story into tasks and estimates the effort required to complete them.
4. Sprint: The Sprint is a time-boxed period (typically 2-4 weeks) during which the Development Team works to complete the selected user stories.
5. Daily Scrum: The Development Team holds a daily stand-up meeting to review progress, discuss any roadblocks, and plan the day ahead.
6. Sprint Review: At the end of the Sprint, the Development Team presents the completed work to the Product Owner and stakeholders in a Sprint Review meeting.
7. Sprint Retrospective: The Development Team holds a Sprint Retrospective meeting to reflect on the Sprint and identify areas for improvement.

Scrum is an iterative and incremental approach to software development that focuses on delivering value to the customer. It emphasizes collaboration, flexibility, and continuous improvement, and is widely used in the software industry to manage complex projects.

KANBAN

Kanban is an Agile project management methodology that emphasizes visualizing the work, limiting work in progress, and optimizing the flow of work through the system. Here’s a brief summary of the Kanban framework:

1. Visual Board: A visual board is used to represent the workflow and visualize the work items as they move through the process. It typically includes columns that represent different stages of the process, such as “To Do,” “In Progress,” and “Done.”
2. Work in Progress (WIP) Limits: WIP limits are used to limit the number of work items that can be in progress at any given time. This helps to prevent overloading the system and promotes a focus on completing work before starting new tasks.
3. Pull System: A pull system is used to control the flow of work by allowing team members to pull work items into the system as they have capacity, rather than pushing work into the system based on a schedule.
4. Continuous Improvement: Kanban emphasizes continuous improvement by encouraging teams to identify and eliminate bottlenecks, improve workflows, and optimize the flow of work through the system.
5. Service Delivery: Kanban can be used to manage not only software development but also any process that involves the delivery of a service, such as IT support, marketing campaigns, or customer service.

Kanban is a flexible and adaptive approach to project management that is suitable for both small and large teams, as well as for a wide range of industries and processes. It emphasizes continuous improvement and focuses on delivering value to the customer.

SCRUMBAN

ScrumBan is a hybrid Agile methodology that combines the principles and practices of Scrum and Kanban. It was created to address the limitations of using either Scrum or Kanban alone and to provide a more flexible approach to project management. Here are some key features of ScrumBan:

1. Lean principles: ScrumBan is rooted in the lean principles of continuous improvement, flow, and value delivery. It emphasizes the importance of reducing waste, optimizing flow, and delivering value to customers.
2. Iterative and incremental: Like Scrum, ScrumBan is an iterative and incremental approach to software development. It emphasizes regular releases and focuses on delivering small, incremental improvements to the product.
3. Visual management: Like Kanban, ScrumBan uses visual management tools to visualize the work, limit work in progress, and optimize the flow of work through the system. This helps to identify bottlenecks, track progress, and improve collaboration.
4. Flexibility: ScrumBan is more flexible than Scrum or Kanban alone, allowing teams to adapt to changing requirements and conditions. It allows for the use of both time-based and flow-based processes, as well as the incorporation of Lean Startup and DevOps practices.
5. Continuous improvement: ScrumBan emphasizes continuous improvement by encouraging teams to regularly review their processes, identify areas for improvement, and make changes to optimize their workflow.

ScrumBan is ideal for teams that need a balance between the structure and rigor of Scrum and the flexibility and adaptability of Kanban. It allows teams to continuously improve their processes, optimize their workflow, and deliver value to customers in a more efficient and effective way.

How to scale agile?

View more http://jordimarti.tech/agile-at-scale

1. http://www.pmi.org/learning/library/pmbok-rup-it-projects-financial-7094 [↩]

Buy Me a Coffee