Agile Project Management methods

1. Agile Project Management
SCRUM
By
Marwa Salim
Asma Abdullah

2. The definition of agile
management
* Agility that is flexibility, it is a state of dynamic,
adapted to the specific circumstances, catering to
the change and self-improvement
* Agile project management is a software project
management coping with constant change and
uncertainty of the project.
* Agile is an attitude rather than a process, is also an
atmosphere rather than a way, of which a most
important term is innovation.

3. Agile Project Management
 is related to the rolling wave planning and
scheduling project methodology.
 Uses iterations (“time boxes”) to develop a
workable product that satisfies the customer
and other key stakeholders.
 Stakeholders and customers review progress
and re-evaluate priorities to ensure alignment
with customer needs and company goals.
 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.

4. Iterative, Incremental Product
Development

5. Traditional Projcet managment
versus Agile Methods
 Traditional methods of software development
have many disadvantages:
 huge effort during the planning phase
 poor requirements conversion in a rapid
changing environment
 treatment of staff as a factor of production
 New methods:
 Agile Software Development

6. Advantages of Agile PM:
 Useful in developing critical breakthrough
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.

7. Qualities:
 Minimize risk - short iterations
 Real-time communication (prefer face-to-
face) -very little written documentation
 Indicated for unpredictable / rapidly
changing requirements

8. Agile methods:
 Scrum
 Extreme Programming
 Adaptive Software Development (ASD)
 Feature Driven Development (FDD)
 Rational Unified Process (RUP)
 Dynamic System Development Method
(DSDM)

9. While each of these methods has unique elements
and applications, most are
based on the following Agile principles:
 • Focus on customer value—Employ business-driven
prioritizations of requirements and features.
 • Iterative and incremental delivery—Create a flow of value
to customers by “chunking” project delivery into small,
functioning Increments.
 • Experimentation and adaptation—Test assumptions early
and build working prototypes to solicit customer feedback
and refine product requirements.
 • Self-organization—Team members decide amongst
themselves who and what should be done.
 • Continuous improvement—Teams reflect, learn, and adapt
to change; work informs the plan.

10. 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.

11. SCRUM
 SCRUM is an agile, lightweight process for
managing and controlling software and product
development using iterative , incremental
practices.
 SCRUM as agile methods in the importance
practice on software development, with
characteristics of relatively flexible organization
system , timely and interactive feedback , can
solve the difficulties faced by traditional methods
some to large extent.
 SCRUM generates the benefits of agile
development with the advantages of a simple
implementation.

12.  A feature is defined as a piece of a product
that delivers some useful functionality to a
customer
 Features are prioritized by their perceived
highest value.
 The project team tackles the highest, feasible
priority features first.
 Priorities are re-evaluated after each iteration.
 Iterations are called sprints and should last no
longer than four weeks.
Scrum uses product features as
deliverables.

13. Specific features are created
according to four distinct phases:
analysis
Design
Build
Test

14. Scrum Development Process

15. 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.

16. Scrum Meetings
 Sprint Planning
 Daily Scrum
 Sprint Review
 Sprint Retrospective

17. SCRUM Meetings