Scribd
Upload
25 views19 pages

Agile Project Management - Session 1

Uploaded by

Abhinav Pandey
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
25 views19 pages

Agile Project Management - Session 1

Uploaded by

Abhinav Pandey
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Agile Project

Management
Introduction
Traditional Projects
Traditional Project Management
● ̌The traditional approach to projects and project management started by defining
exactly what the project was expected to produce.

● This was termed the requirements or specification and was agreed and signed off
between the project team and the business or customer.

● The project team then went away and built a product or system that they thought met
those requirements and, some time later, presented the finished product to the customer.

● The problems with this approach was that the end result was all too often that it was not
what the customer needed.
Benefits Disadvantages
● Clearly defined objectives - Everything ● Rigidity - Since this methodology is
is pre-planned so each team member based on pre-planning and executing,
knows their responsibilities and the when things unexpectedly go wrong,
project's requirements ahead of time
the team can find themselves stuck,
● Controlled processed - The project
having to improvise on the spot, going
manager has most of the control in a
outside the plan of action, and simply
traditional setup and almost all changes
hoping for the best. And in some
have to be approved by this individual
before they can be implemented. This situations, the project team is forced
allows for minimal deviation from the plan to go back to the drawing board and
that was devised during scope create a new plan from the ground up.
management. ● Less Customer Input - When
● Singular accountability - Project establishing a plan with traditional
manager has all the power. project management, the customer or
● Clear documentation - Standardised client is looped in at the start. Their
document from start to finish. opinion isn’t needed during the rest of
● Cost Effectiveness - Projects that use a the development process until the end
traditional method are usually easier to result is ready to be presented. This
complete, taking less time from start to means there are few opportunities for
finish as there are very few last minute
customer collaboration with the
changes.
development teams.
The Agile Manifesto
• Individuals and Interactions: in an agile
development, self-organization and
We are uncovering better ways of developing software by motivation are important, as are interactions
doing it and helping others do it. Through this work we like co-location and pair programming

have come to value: • Working Software: working software will


be much more useful and welcome than just
● Individuals and interactions over processes and tools presenting detailed documents to clients in
● Working software over comprehensive meetings
documentation
● Customer collaboration over contract negotiation • Customer Collaboration: requirements
● Responding to change over following a plan cannot be fully defined at the beginning of the
software development cycle, therefore
That is, while there is value in the items on the right, we continuous customer involvement is very
value the items on the left more. important

• Responding to Change: agile


development is focused on quick responses to
change and continuous development,
harnessing change for the customer’s
competitive advantage
Agile Project Management
● ̌Agile methodology is an iterative approach to software development.

● There are no predefined phases at the beginning of the project. Rather, the agile approach
is to work in short iterations.

● Each iteration is converted into a valuable software piece, allowing developers to respond
quickly to the changes as per the stakeholder’s requirements and feedback. This ensures
the product is developed as per the needs and is well-refined.

● What is fixed and agreed between the project team and the customer is the resources that
will be used and the time that will be taken by the project team to deliver as much as
possible of the prioritized features the customer wants.
Principles of Agile Project Management
Principles of Agile Project Management
Agile Project Management vs Traditional Project Management

● Role of Project Manager: Command & Control vs Facilitator of


Collaboration between developers & business.
● Fixed Requirements vs Fixed Features.
● Early Project Planning vs Planning for each phase, release or
iteration is carried out as late as possible. Further, although the
outline project plan is produced by the project manager, the
detailed plans are produced by the development team.
● Project stages vs Multiple iterations and Product releases.
● The traditional project concept of change control is replaced by the
features backlog. This is a list of prioritized business requirements,
which is controlled by the business.
Agile Project Management vs Traditional Project Management

● Risk Management by Project Manager vs The developers own the


development risks and the business takes a more proactive role as
the product owner.
● Project Manager hands out the work vs Work is managed by the
development team and the project manager takes on more of a
supportive role to the team
● In a traditional project the project manager has a detailed Gantt
chart against which to monitor progress. In an agile project their
role is to record the effort used on a burndown chart.
Benefits of the Agile Methodology
● Overcomes the difficulty that customers have in adequately specifying their requirements in the first place,
before they have even seen some sort of prototype.
● Close involvement of the customer means they can share the decision making, set the priorities and agree on
the best solution to any issues. They will be committed to the final product and it will meet their requirements.
● The use of agile methods ensures that the project delivers a quality product much earlier than would happen on
a traditional project.
● The product will not yet have all of the required features but, as per the Pareto principle, the delivery of the
most important 20% of the features is likely to deliver around 80% of the benefits.
● Using the delivery of a series of working products as the main form of progress measurement is one that
everyone involved in the project can understand.
● By empowering the development team, allowing them to organize themselves and having active customer
involvement the team will be much more highly motivated and produce better results.
● The focus on technical excellence and good design in an agile project coupled with continuous testing will
ensure that a product of excellent quality is delivered.
Many project management practitioners believe that agile methods
do not scale well. Hence large-scale projects (even software
development projects) should probably still be conducted using the
traditional waterfall development and project management methods.
The strength and usefulness of agile methods are both clearly
demonstrated in projects with poorly-defined and frequently changing
requirements. So it would not seem to offer any advantage over
traditional methodology when it comes to projects where the
requirements are clearly defined and unlikely to change significantly
over the course of the project. So large projects with clear
requirements (such as major construction projects) are
probably best managed using the traditional methods.
Agile Methodologies in Action
Agile Methodologies
● Scrum
● Kanban
● Extreme Programming
● Lean Development
● Crystal
Thank You

You might also like