Question

Please help writing a well structured document using the below

Agile Runbook - Our Overall Delivery Process

1. How do we initiate a Project?

Any project is a response to a pain point or desire expressed by either customers, internal stakeholders, employees, or regulatory authorities. In short, a project is a time bound and specific goal oriented task-system that is born out of an ask from any stakeholder.

Project initiation is laying down a new project by defining its goals, objectives, scope, purpose, deliverables and Cost-Benefit Analysis to be produced. It is the first step or phase in the Project Life Cycle. The key steps to initiate a well executed project are:

• Identify and develop a business case.
• Conduct Feasibility study
• Calculate the Project Criticality
• Establish the Project Charter
• Identify stakeholders
• Appoint project team
• Seek review and approval of the project

The Role of PMO:

The PMO provides guidance and support on integrating project processes while promoting the use of tools and templates. The specific duties of PMO will vary depending on the category and criticality of the Project. In general, the PMO fulfills one or more of the following roles:

• PMO helps to ensure that the projects are completed successfully, standardised process are being followed, resources are being used effectively, and accurate information is being used for decision making.
• Rank projects based on a number of important criteria and business drivers.
• Monitor and report all the projects to the Executive Management, the AUB group entities and to all the Project Sponsors
• Enable the project teams with the Project Management tools and procedures for effective project management

Agile project management delivery process:

Agile project management is an approach based on delivering requirements iteratively and incrementally throughout the project life cycle. At the core of agile, is the requirement to exhibit central values and behaviors of trust, flexibility, empowerment and collaboration.

Agile Project Management Events:

Business Owners (BO) will produce an exhaustive list of project initiative which needs to be achieved in the current year

Product Owner (PO) will then select from the list of projects the ones they wish to pursue.

BOs and POs will collaborate in prioritizing these projects for the year.

The Product Owner will then set up his Agile team based on the project requirements, most agile teams comprise of:

1. Scrum Master (SM)
2. Development Team
3. Testers
4. Designers
5. Agile Lead / Analyst
6. Security / Information Security
7. Marketing
8. Legal

Most projects have stages. Agile projects include seven recurring events for project delivery:

• Project planning: Project planning includes creating a product vision statement and a product roadmap.
• Release planning: Planning the next set of product features to release and identifying an imminent product launch date around which the team can mobilize. On agile projects, you plan one release at a time.
• Sprint: A short cycle of development, in which the team creates potentially shippable product functionality. Sprints, sometimes called iterations, typically last between one and four weeks. Sprints can last as little as one day, but should not be longer than four weeks. Sprints should remain the same length throughout the entire project, which enables teams to plan future work more accurately based on their past performance.
• Sprint planning: A meeting at the beginning of each sprint where the scrum team commits to a sprint goal. They also identify the requirements that support this goal and will be part of the sprint, and the individual tasks it will take to complete each requirement.
• Daily scrum: A 15-minute coordination and synchronization meeting held each day in a sprint, where development team members state what they completed the day before, what they will complete on the current day, and whether they have any roadblocks.
• Sprint review: A meeting at the end of each sprint, introduced by the product owner, where the development team demonstrates the working product functionality it completed during the sprint to stakeholders, and the product owner collects feedback for updating the product backlog.
• Sprint retrospective: A meeting at the end of each sprint where the scrum team inspects and adapts their processes, discussing what went well, what could change, and makes a plan for implementing changes in the next sprint.

1. How do we assign resources to an Agile Project?

For Assigning resources in an Agile Project, first, we need to build essential formations of Cross- functional team members, so we can cover as many expertise as needed for the project over time.

Given the shift in work from project managers to Agile teams, Agile Project Management demands that team members know how to work in this new fashion. They must be able to collaborate with each other, as well as with the end users. They must be able to communicate well to keep projects on track. And they should feel empowered to take appropriate actions at the right times in order to keep pace with delivery schedules.

The Core principles of an agile team:

• Customer satisfaction is always the highest priority and is achieved through rapid and continuous delivery.
• Changing environments are embraced at any stage of the process to provide the customer with a competitive advantage.
• A product or service is delivered with higher frequency.
• Stakeholders and developers collaborate closely on a daily basis.
• All stakeholders and team members remain motivated for optimal project outcomes, while teams are provided with all the necessary tools and support, and are trusted to accomplish project goals.
• Face-to-face meetings are deemed the most efficient and effective format for project success.
• A final working product is the ultimate measure of success.
• Sustainable development is accomplished through agile processes whereby development teams and stakeholders are able to maintain a constant and ongoing pace.
• Agility is enhanced through a continuous focus on technical excellence and proper design.
• Simplicity is an essential element.
• Self-organizing teams are most likely to develop the best architectures and designs to meet requirements.
• Regular intervals are used by teams to improve efficiency through fine-tuning behaviors.

Agile project management is an approach based on delivering requirements iteratively and incrementally throughout the project life cycle. At the core of agile is the requirement to exhibit central values and behaviors of trust, flexibility, empowerment and collaboration. The main benefit of Agile Project Management is its ability to respond to issues as they arise throughout the course of the project. Making a necessary change to a project at the right time can save resources and, ultimately, help deliver a successful project on time and within budget.

Agile teams build rapid feedback, continuous adaptation and QA best practices into their iterations. They adopt practices such as continuous deployment (CD) and continuous integration (CI), using technology that automates steps to speed up the release and use of products.

Additionally, Agile Project Management calls for teams to continuously evaluate time and cost as they move through their work. They use velocity, burn down and burn up charts to measure their work, instead of Gantt charts and project milestones to track progress.

These six phases conclude the full Agile method lifecycle model

• Concept: Projects and the viability are envisioned and prioritised according to importance.
• Inception: A team is brought together, team members are individually identified, a fund is put in place and any initial requirements are discussed and decided.
• Iteration/Construction: The project team begins to work on the project’s development using software implemented with the agile method focusing on iteration requirements and feedback.
• Release: Quality testing, training, both internal and external and documentation and reporting are put into production.
• Production: The Agile methods helps to keep track of your project and make sure it is constantly optimised and ready to bounce back from any sudden changes or uncertainties.
• Retirement: Post implementation activities.

Advantages of developing agile teams in project management:

• More rapid deployment of solutions
• Reduced waste through minimization of resources
• Increased flexibility and adaptability to change
• Increased success through more focused efforts
• Faster turnaround times
• Faster detection of issues and defects
• Optimized development processes
• A lighter weight framework
• Optimal project control
• Increased focus on specific customer needs
• Increased frequency of collaboration and feedback

Answer 1

Title of Contents :

1. Introduction
2. Agile Runbook – Our Overall Delivery Process
3. Role of PMO (Project Management Office)
4. Agile Project Management Events
5. Activities in Agile Projects
6. Resource Assignment
7. Core Principles Of Agile Project Management
8. Execution in Agile Project Philosophy
9. Phases of Agile Project Lifecycle
10. Advantages of Using Agile Approach

Introduction :

Project Management is an art and it takes efforts and experience to perfect it. There are lot of guidelines which are available from PMBOK on how to run the projects. The most widely used methods are Waterfall method and Agile delivery method. Both of them have their own advantages and disadvantages. For instance, in case of construction project, each activity needs to follow a well defined structure and sequence of activity. This is a classic example of waterfall method wherein all the requirements need to be captured upfront, plans need to be defined and constant monitoring needs to be done to ensure the project is running as per the plan. In case of a new product development, faster results will be more helpful and they will help in identifying what is right and what can be changed. Agile methodology helps in such circumstances. In this document, we take a closer look at the Agile project methodology.

Agile Runbook - Our Overall Delivery Process

How do we initiate a Project?

Any project is a response to a pain point or desire expressed by either customers, internal stakeholders, employees, or regulatory authorities. In short, a project is a time bound and specific goal oriented task-system that is born out of an ask from any stakeholder.Project initiation is laying down a new project by defining its goals, objectives, scope, purpose, deliverables and Cost-Benefit Analysis to be produced. It is the first step or phase in the Project Life Cycle.

The key steps to initiate a well executed project are:

• Identify and develop a business case.
• Conduct Feasibility study
• Calculate the Project Criticality
• Establish the Project Charter
• Identify stakeholders
• Appoint project team
• Seek review and approval of the project

The Role of PMO(Project Management Office):

One of the key aspects of effective project management is the PMO. The PMO provides guidance and support on integrating project processes while promoting the use of tools and templates. The specific duties of PMO will vary depending on the category and criticality of the Project. In general, the PMO fulfils one or more of the following roles:

• PMO helps to ensure that the projects are completed successfully, standardised process are being followed, resources are being used effectively, and accurate information is being used for decision making.
• Rank projects based on a number of important criteria and business drivers.
• Monitor and report all the projects to the Executive Management, the AUB group entities and to all the Project Sponsors
• Enable the project teams with the Project Management tools and procedures for effctive project management
  

Agile project management delivery process:

Agile project management is an approach based on delivering requirements iteratively and incrementally throughout the project life cycle. At the core of agile, is the requirement to exhibit central values and behaviors of trust, flexibility, empowerment and collaboration.

Agile Project Management Events:

In agile project methodology, there are few main actors who need to play an active role. They are Product owner, Scrum master and the development team.

Business Owners (BO) will produce an exhaustive list of project initiative which needs to be achieved in the current year. Product Owner (PO) will then select from the list of projects the ones they wish to pursue. BOs and POs will collaborate in prioritizing these projects for the year.

The Product Owner will then set up his Agile team based on the project requirements, most agile teams comprise of:

1. Scrum Master (SM)
2. Development Team
3. Testers
4. Designers
5. Agile Lead / Analyst
6. Security / Information Security
7. Marketing
8. Legal

Activities in Agile Projects:

Agile projects include seven recurring events for project delivery:

• Project planning: Project planning includes creating a product vision statement and a product roadmap.
• Release planning: Planning the next set of product features to release and identifying an imminent product launch date around which the team can mobilize. On agile projects, you plan one release at a time.
• Sprint: A short cycle of development, in which the team creates potentially shippable product functionality. Sprints, sometimes called iterations, typically last between one and four weeks. Sprints can last as little as one day, but should not be longer than four weeks. Sprints should remain the same length throughout the entire project, which enables teams to plan future work more accurately based on their past performance.
• Sprint planning: A meeting at the beginning of each sprint where the scrum team commits to a sprint goal. They also identify the requirements that support this goal and will be part of the sprint, and the individual tasks it will take to complete each requirement.
• Daily scrum: A 15-minute coordination and synchronization meeting held each day in a sprint, where development team members state what they completed the day before, what they will complete on the current day, and whether they have any roadblocks.
• Sprint review: A meeting at the end of each sprint, introduced by the product owner, where the development team demonstrates the working product functionality it completed during the sprint to stakeholders, and the product owner collects feedback for updating the product backlog.
• Sprint retrospective: A meeting at the end of each sprint where the scrum team inspects and adapts their processes, discussing what went well, what could change, and makes a plan for implementing changes in the next sprint.

Resource Assignment : How do we assign resources to an Agile Project?

For Assigning resources in an Agile Project, first, we need to build essential formations of Cross- functional team members, so we can cover as many expertise as needed for the project over time.

Given the shift in work from project managers to Agile teams, Agile Project Management demands that team members know how to work in this new fashion. They must be able to collaborate with each other, as well as with the end users. They must be able to communicate well to keep projects on track. And they should feel empowered to take appropriate actions at the right times in order to keep pace with delivery schedules.

Core Principles Of Agile Project Management:

The Core principles of an agile team:

• Customer satisfaction is always the highest priority and is achieved through rapid and continuous delivery.
• Changing environments are embraced at any stage of the process to provide the customer with a competitive advantage.
• A product or service is delivered with higher frequency.
• Stakeholders and developers collaborate closely on a daily basis.
• All stakeholders and team members remain motivated for optimal project outcomes, while teams are provided with all the necessary tools and support, and are trusted to accomplish project goals.
• Face-to-face meetings are deemed the most efficient and effective format for project success.
• A final working product is the ultimate measure of success.
• Sustainable development is accomplished through agile processes whereby development teams and stakeholders are able to maintain a constant and ongoing pace.
• Agility is enhanced through a continuous focus on technical excellence and proper design.
• Simplicity is an essential element.
• Self-organizing teams are most likely to develop the best architectures and designs to meet requirements.
• Regular intervals are used by teams to improve efficiency through fine-tuning behaviors.

Execution in Agile Project Philosophy

Agile project management is an approach based on delivering requirements iteratively and incrementally throughout the project life cycle. At the core of agile is the requirement to exhibit central values and behaviors of trust, flexibility, empowerment and collaboration. The main benefit of Agile Project Management is its ability to respond to issues as they arise throughout the course of the project. Making a necessary change to a project at the right time can save resources and, ultimately, help deliver a successful project on time and within budget.

Agile teams build rapid feedback, continuous adaptation and QA best practices into their iterations. They adopt practices such as continuous deployment (CD) and continuous integration (CI), using technology that automates steps to speed up the release and use of products.

Additionally, Agile Project Management calls for teams to continuously evaluate time and cost as they move through their work. They use velocity, burn down and burn up charts to measure their work, instead of Gantt charts and project milestones to track progress.

Phases of Agile Project Lifecycle

These six phases conclude the full Agile method lifecycle model

• Concept: Projects and the viability are envisioned and prioritised according to importance.
• Inception: A team is brought together, team members are individually identified, a fund is put in place and any initial requirements are discussed and decided.
• Iteration/Construction: The project team begins to work on the project’s development using software implemented with the agile method focusing on iteration requirements and feedback.
• Release: Quality testing, training, both internal and external and documentation and reporting are put into production.
• Production: The Agile methods helps to keep track of your project and make sure it is constantly optimised and ready to bounce back from any sudden changes or uncertainties.
• Retirement: Post implementation activities.

Advantages of Using Agile Approach

Advantages of developing agile teams in project management:

• More rapid deployment of solutions
• Reduced waste through minimization of resources
• Increased flexibility and adaptability to change
• Increased success through more focused efforts
• Faster turnaround times
• Faster detection of issues and defects
• Optimized development processes
• A lighter weight framework
• Optimal project control
• Increased focus on specific customer needs
• Increased frequency of collaboration and feedback