Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Agile Project Management

No description
by

Alexis Resendiz A.

on 19 March 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Project Management

Agile Project Management
Projects are not new in the world!
Agile phases
A brief history...
An approaching to the agile project management
1950
1960
1980
1970
1940
1930
IID (Interative and Incremental Development)
Militaries uses IDD for the develop of the X-15 hypersonic jet, also it is used for its software development
IBM'S Federal Systems Division andTRW complete $100m+ projects using iterative methods
Object Oriented programming articulates the "spiral development method"
Plan - Do- Study - Act (PDSA)
Walter Shewhart conceptualizes short life cycle projects
U.S. scientist work on rapidly developing theoretic atomic bomb
Necessity of new strategies to work efficiently, quickly due to the wars.
Jeff Sutherland and Ken Schwaber create Scrum approach
1990
2001. Agile Alliance is created and the term "agile methods" appears

2004. Scrum Alliance formed.

2000+
In this phase is generated documents witch satisfy the initiation phase of the project.

This includes:
- The project charter
- Work Breakdown Structure
- Risk Analysis
- Communication Plan
- Stakeholder Analysis

Monitoring and Controlling
Is oversees all the tasks and metrics necessary to ensure that the approved and authorized project is within scope, on time, and on budget.

1. Project Initiation
Conclusion
IBM recognizes the value of iterative refinement
In a simple way, agile is a description for project management methodologies that focus on people, communications, the product, and flexibility.

A methodology does not ensure that a project will success!

Better product quality
Higher customer satisfaction
It is the most consistent project management technique since it involves frequent testing of the project under development.
Higher team morale
Increased collaboration and ownership
Customized team structures
More relevant metrics
Improved performance visibility
Increased project control
Improved project predictability
Reduced risk

Active user involvement and close collaboration are required throughout the development cycle.
Agile Requirements Are Barely Sufficient: Agile development teams capture requirements at a high level and on a piecemeal basis, just-in-time for each feature to be developed.
Testing is integrated throughout the lifecycle.
If the team members are not committed, the project will either never complete or fail.
This methodology needs experienced team members only. If the team consists of people who are novices, the project cannot be completed in time.
If any of the team members leave during a development it can have a huge inverse effect on the project development.

In this phase the nature and scope are determined after business environment of the project.
1. Project Initiation
2. Project Planning
Project Planning maps to Release Planning for an Agile project.
It's an iterative phase that is repeated with each Sprint.
4. Project closure
It consists in finalize all activities across all of the process groups to formally close the project or a project phase.

How do agile projects works?
Transparency
: Means that everyone involved on an agile project knows what is going on and how the project is progressing.

Frequent inspection:
The people who are invested in the product and process the most should regularly evaluate the product and process.

Adaptation:
Make adjustments quickly to minimize problems; if inspection shows something that needs to be fixed, it’s necessary to change it.
Full transcript