Power Point Presentation On

“Agile Project Management”

Submitted By:- Shourja Ganguly
CSE1-7th Sem
Project Management and Entrepreneurship
HSMC-701
16900219031
 What is Agile Project Management?
Agile project management is an iterative approach to software development projects
and ensures feedback can be acted on quickly and that responsive changes can be
made at each stage of a sprint or product cycle. This allows project teams to adopt
agile project management methodologies to work quickly and collaboratively within
the timeframe and budget of a project.
Most current agile project management methods have their roots in software
development. Back in the 1990s, software teams were finding that the highly
structured “heavyweight” traditional project management methodologies (for example,
Waterfall) just weren’t cutting it when it came to the way they needed to work. They
were finding that the pitfalls of these heavyweight methods — such as a lack of
flexibility, adaptability, and even autonomy — made it more difficult for them to
respond to change or incorporate their learnings as they worked. As the project plans
were outlined at the outset, there was no room for surprise, and deviations could be
costly. Instead of being held captive by the project management plan they outlined at
the start, agile project management methods meant that teams could take those
changes into consideration to make the best possible product. To do this, they needed
shorter development cycles (called sprints), a more iterative process, and continuous
 feedback and testing.

Traditional PM versus Agile Methods

• Agile Project Management (Agile PM)

1. Relies on incremental, iterative development

• Traditional PM Approach cycles to complete less-predictable projects. 2. Is
ideal for exploratory projects in which
requirements need to be discovered and new
1. Concentrates on thorough, upfront technology tested.
planning of the entire project.
3. Focuses on active collaboration between the
project team and customer representatives.
2. Requires a high degree of predictability to be
effective.

Traditional Project Management versus

Agile Project Management
 • Agile
1. Continuous design
• Traditional 2. Flexible
1. Design up front 3. Features/requirements
2. Fixed scope 4. Freeze design as late as possible
3. Deliverables 5. High uncertainty
4. Freeze design as early as possible 6. Embrace change
5. Low uncertainty
7. High customer interaction
6. Avoid change 8. Self-organized project teams
7. Low customer interaction
8. Conventional project teams
Project Uncertainty
Agile project management
• Is related to the rolling wave planning and scheduling project
methodology. 1. Uses iterations ("time boxes") to develop a workable product that
satisfies the customer and other key stakeholders.
2. Stakeholders and customers review progress and re-evaluate priorities to ensure
alignment with customer needs and company goals.
3. Adjustments are made and a different iterative cycle begins that subsumes the work of
the previous iterations and adds new capabilities to the evolving product.

Iterative, Incremental Product Development

Advantages of Agile PM
• Useful in developing critical break through technology or defining essential
features
• Continuous integration, verification, and validation of the evolving
product. • Frequent demonstration of progress to increase the likelihood that
the end product will satisfy customer needs.
• Early detection of defects and problems.
Agile PM Principles
Popular Agile PM Methods
 Agile PM in Action: Scrum
• Scrum Methodology
1. Is a holistic approach for use by a cross-functional team collaborating to develop a
new product.
2. Defines product features as deliverables and prioritizes them by their perceived
highest value to the customer.
3. Re-evaluates priorities after each iteration (sprint) to produce fully functional
features.
4. Has four phases: analysis, design, build, test
Key Roles and Responsibilities in the Scrum
Process
• Product Owner
• Acts on behalf of customers to represent their interests.
• Development Team
• Is a team of five-nine people with cross-functional skill sets is responsible for delivering
the product.
• Scrum Master (aka Project Manager)
• Facilitates scrum process and resolves impediments at the team and organization level
by acting as a buffer between the team and outside interference.

Applying Agile to Large Projects

• Scaling
• Is using several teams to work on different features of a large scale project at the same
 time.

• Staging
• Requires significant up-front planning to manage the interdependences of different
features to be developed.
• Involves developing protocols and defining roles to coordinate efforts and assure
compatibility and harmony.

Limitations and Concerns of Agile PM

• It does not satisfy top management's need for budget, scope, and schedule
control.
• Its principles of self-organization and close collaboration can be incompatible
with corporate cultures.
• Its methods appear to work best on small projects that require only five-nine
 dedicated team members to complete the work.
• It requires active customer involvement and cooperation.
Conclusion
These are the most basic and important parts of Agile project management. As
we transition our team to an Agile methodology, these processes, Agile software
and tools, roles, and principles will help you change your mindset and begin
working together to be more flexible and adapt to changes as they come. Agile
isn’t for everyone, but teams who use it correctly will experience enormous
benefits, including streamlined work processes and rapid innovation.

Bibliography
• https://www.workfront.com/projectmanagement/methodologies/agile
• https://www.teamwork.com/project-management-guide/agile-project
management/
• https://www.atlassian.com/agile/project-management