agile delivery

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

Upload: bruno-portaluri

Post on 08-Jul-2015

488 views

Category:

Leadership & Management


1 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Agile Delivery

© 2014 IBM Corporation

Agile Project Management practicesfrom the field

Bruno Portaluri

Maximo Technical Solution Architect

Last Update: 2014-11-13

Page 2: Agile Delivery

© 2014 IBM Corporation2

Agile Timeline

MassProduction

Waterfall

RUP Agile

Lean Manufacturing

Lean SoftwareDevelopment

1900 1950 1980 200019901970

Page 3: Agile Delivery

© 2014 IBM Corporation3

Traditional Project Management Roots

Page 4: Agile Delivery

© 2014 IBM Corporation4

Positivism

Knowledgeis a

finite and achievable

objective

Traditional Project Management Roots

Page 5: Agile Delivery

© 2014 IBM Corporation5

Agile Project Management Roots

Postmodernismemphasizes

uncertainty and unpredictability in human affairs

Agile Project Management is skepticalabout single narrative accounts

of how organizations are developing.

It encourages diversityand to a degree disharmony, argument and conflict,

as well as a form of relativism in whichdifferent positions have a right to be heard.

Page 6: Agile Delivery

© 2014 IBM Corporation6

Manifestofor

Agile Software Development

(2001)

Page 7: Agile Delivery

© 2014 IBM Corporation7

Individuals and interactionsover processes and tools

Page 8: Agile Delivery

© 2014 IBM Corporation8

Working softwareover comprehensive documentation

Page 9: Agile Delivery

© 2014 IBM Corporation9

Customer collaborationover contract negotiation

Page 10: Agile Delivery

© 2014 IBM Corporation10

Responding to changeover following a plan

Page 11: Agile Delivery

© 2014 IBM Corporation11

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.

Page 12: Agile Delivery

© 2014 IBM Corporation12

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.

Page 13: Agile Delivery

© 2014 IBM Corporation13

Requirements…

Page 14: Agile Delivery

© 2014 IBM Corporation14

Page 15: Agile Delivery

© 2014 IBM Corporation15

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

Page 16: Agile Delivery

© 2014 IBM Corporation16 © 2014 IBM Corporation16

Bruno PortaluriMaximo Technical Solution Architect

eMail: [email protected]

Twitter: @bportaluri

Blog: MaximoDev