A quick presentation to explain the core Agile Development principles and how to adopt them in the real world.

1. © 2014 IBM Corporation
Bruno Portaluri
Maximo Technical Solution Architect
Agile Project Management practices
from the field
Last Update: 2014-11-13

2. Agile Timeline
Mass
Production
Lean Manufacturing
Waterfall
Lean Software
Development
RUP Agile
1900 1950 1970 1980 1990 2000
2 © 2014 IBM Corporation

3. Traditional Project Management Roots
3 © 2014 IBM Corporation

4. Traditional Project Management Roots
Positivism
Knowledge
is a
finite and achievable
objective
4 © 2014 IBM Corporation

5. Agile Project Management Roots
Postmodernism
emphasizes
uncertainty and unpredictability in human affairs
Agile Project Management is skeptical
about single narrative accounts
of how organizations are developing.
It encourages diversity
and to a degree disharmony, argument and conflict,
as well as a form of relativism in which
different positions have a right to be heard.
5 © 2014 IBM Corporation

6. Manifesto
for
Agile Software Development
(2001)
6 © 2014 IBM Corporation

7. Individuals and interactions
over processes and tools
7 © 2014 IBM Corporation

8. Working software
over comprehensive documentation
8 © 2014 IBM Corporation

9. Customer collaboration
over contract negotiation
9 © 2014 IBM Corporation

10. Responding to change
over following a plan
10 © 2014 IBM Corporation

11. Twelve Principles of Agile Software (1/2)
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.
11 © 2014 IBM Corporation

12. Twelve Principles of Agile Software (1/2)
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.
12 © 2014 IBM Corporation

13. Requirements…
13 © 2014 IBM Corporation

14. 14 © 2014 IBM Corporation

15. Start adopting Agile practices NOW
• Product ‘backlog’
• Iterative planning
• Iterative delivery
• Phased rollout (beta program with advanced key users)
• Stop writing documents or making calls and put people
together asking them to build a solution prototype
(PoT/PoC)
• Use the prototype as a starting point for your project
• Partner with your customer
• Throw away Microsoft Project
• Try your own way
15 © 2014 IBM Corporation

16. Bruno Portaluri
Maximo Technical Solution Architect
eMail: bruno.portaluri@it.ibm.com
Twitter: @bportaluri
Blog: MaximoDev
16 © 2014 IBM Corporation