Scribd
Upload
19 views10 pages

SPM Week 4 - Agile PM

Uploaded by

Mohammad Zawar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
19 views10 pages

SPM Week 4 - Agile PM

Uploaded by

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

Chapter 3

• Importance of Agile Development for Project Manager

1
The Manifesto for
Agile Software Development
“We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
•Individuals and interactions over processes
and tools
•Working software over comprehensive
documentation
•Customer collaboration over contract
negotiation
•Responding to change over following a plan
That is, while there is value in the items on the
right, we value the items on the left more.”
Kent Beck et al

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2
2009) Slides copyright 2009 by Roger Pressman.
What is “Agility”?
• Effective (rapid and adaptive) response to change
• Effective communication among all stakeholders
• Drawing the customer onto the team
• Organizing a team so that it is in control of the work
performed
Yielding …
• Rapid, incremental delivery of software

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 3
2009) Slides copyright 2009 by Roger Pressman.
Agility and the Cost of Change

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 4
2009) Slides copyright 2009 by Roger Pressman.
An Agile Process
• Is driven by customer descriptions of what is required
(scenarios)
• Recognizes that plans are short-lived
• Develops software iteratively with a heavy emphasis on
construction activities
• Delivers multiple ‘software increments’
• Adapts as changes occur

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 5
2009) Slides copyright 2009 by Roger Pressman.
Agility Principles - I
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily
throughout the project.
5. Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information
to and within a development team is face–to–face conversation.

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 6
2009) Slides copyright 2009 by Roger Pressman.
Agility Principles - II
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The
sponsors, developers, and users should be able to maintain a
constant pace indefinitely.
9. Continuous attention to technical excellence and good
design enhances agility.
10. Simplicity – the art of maximizing the amount of work not done
– is essential.
11. The best architectures, requirements, and designs emerge from
self–organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 7
2009) Slides copyright 2009 by Roger Pressman.
Human Factors
• the process molds to the needs of the people and team, not the other
way around
• key traits must exist among the people on an agile team and the
team itself:
• Competence.
• Common focus.
• Collaboration.
• Decision-making ability.
• Fuzzy problem-solving ability.
• Mutual trust and respect.
• Self-organization.

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 8
2009) Slides copyright 2009 by Roger Pressman.
Scrum
• Originally proposed by Schwaber and Beedle
• Scrum—distinguishing features
• Development work is partitioned into “packets”
• Testing and documentation are on-going as the product is constructed
• Work occurs in “sprints” and is derived from a “backlog” of existing
requirements
• Meetings are very short and sometimes conducted without chairs
• “demos” are delivered to the customer with the time-box allocated

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 9
2009) Slides copyright 2009 by Roger Pressman.
Scrum

These slides are designed to accompany Software


Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 10
2009) Slides copyright 2009 by Roger Pressman.

You might also like