Sei sulla pagina 1di 42

AGILE PROJECT MANAGEMENT

Allen Evitts
2016
Program Outline
What is Agile?
Projects & Project Management in an Agile world
Agile and Scrum
Common Scrum Terminology
Other Iterative methods
Using Agile outside Software Development
Communication skills and Agile
Case studies of transitioning to Agile
Critique of Agile
Conclusion and Future of Agile
AGILE AND SCRUM
What is Agile?
What is Agile?
History of Iterative Methods in Software Development
Spiral
Extreme
Agile
Ongoing Stakeholder involvement
Agile Manifesto
Evolutions
The 12 principles of the Agile Manifesto by Fowler and
Highsmith (2001) are:
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 for 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 with and within a development team is face-to-face
conversation.
Agile Manifesto Principles cont
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. Simplicitythe art of maximizing the amount of work
not doneis 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.
Agile Manifesto values:
Individuals and interactions over processes and tools
Working osftware over comprehenxive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
The Value of Agile
Speed to Market
Flexibility
Risk Management
Cost Control
Quality
Right Product
Transparency
Misconceptions about Agile
Its new Its different.
Can it work with a Fixed Budget?
Its too unpredictable
Features are controlled by the developers
Strategic goals arent considered
The technology teams will required to work more closely
together and with the business.
Agile Lifecycle
Planning
Execution
Review
Reset and Repeat
Key Agile Definitions
Sprint
Backlog
User Stories: I (the user) wants to do (something) so that I can
accomplish (goal).
Sprint Planning
Review and understand the goals of the project
Review the resources assigned to the project
Determine the key decision maker
(customer/stakeholder/sponsor)
Create Project Backlog
Determine whats first to be created
Get the team on the same page
Backlog
Estimations
The Sprint
Daily Standup
What did you do yesterday?
What are you going to do today?
Do you need any help or are there any blockers in the way?
Keys to Success
Good Planning
Team work
Communications
Evolutions
Scrum Alliance
The Software Craftmanship Manifesto
Guide to Agile Practices
Agile principle included in PMI and Prince 2 and IIBM bodies
of knowledge.
PROJECTS & PROJECT
MANAGEMENT IN AN AGILE
WORLD
Projects & Project Management in an Agile world

Basics of Projects
What is a project/program/portfolio?
Why we have projects in organizations?
Role of the Project Manager
Role of the Business Analyst
Role of the Developer
Role of the Client / Customer
AGILE AND SCRUM
Agile and Scrum
Agile Manifesto
Scrum principles
COMMON SCRUM TERMINOLOGY
OTHER ITERATIVE METHODS
Other Iterative methods
1. Spiral Methodology
2. Lean Kanban
3. Extreme Programming (XP)
4. Crystal Methods
5. Dynamic Systems Development Methods (DSMD)
6. Feature Driven Development (FDD)
7. Test Driven Development (TDD)
8. Adaptive Software Development (ASD)
9. Agile Unified Process (AUP)
10. Domain-Driven Design (DDD)
Spiral Methodology
Lean Kanban
Extreme Programming (XP)
XP values:
communication,
feedback,
simplicity,
courage.
Roles in the XP approach include:
customer,
developer,
tracker,
coach.
Crystal Methods
Dynamic Systems Development Methods (DSMD)
Feature Driven Development (FDD)
Test Driven Development (TDD)
Adaptive Software Development (ASD)
Agile Unified Process (AUP)
Domain-Driven Design (DDD)
USING AGILE OUTSIDE
SOFTWARE DEVELOPMENT
CASE STUDIES OF
TRANSITIONING TO AGILE
CRITIQUE OF AGILE

Potrebbero piacerti anche