Your SlideShare is downloading. ×
Agile project management
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile project management


Published on

Published in: Technology, Business

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 3. WHAT IS AGILE????? Agile project management is an iterative and incremental method of managing the design and build activities for engineering, information technology, and new product or service development projects in a highly flexible and interactive manner. An alternative way of managing software projects With different values and principles to traditional development Incremental, iterative and collaborative, rather than distinct stages
  • 4. How Agile Differs from Traditional Development Approach Traditional – Sequential Method initiation Req anal. Design Code Test deplo yment
  • 5. Agile – Iterative Method Sprint1 Delivery Sprint2 Delivery
  • 6. AGILE MANIFESTO… The agile manifesto is the most important statement which really pitch forked this methodology to a different level. •Individuals and interactions over processes and tools •Working software over comprehensive documentation •Customer collaboration over contract negotiation •Responding to change over following a plan
  • 7. • Let team & users cooperate • Become a facilitator Individuals and interactions over processes and tools • Focus on delivery • Don’t abandon documentation Working software over comprehensive documentation CONTINUED…
  • 8. • Customer vision is at center • Manage relationships not contracts Customer collaboration over contract negotiation • Let customers change their mind • Use change-friendly methodologies Responding to change over following a plan CONTINUED…
  • 9. Within agile development, Scrum has the most to say about exactly what is agile project management. So let’s use Scrum as our model for answering this question. On a Scrum project, there are three roles: product owner, ScrumMaster and team. The product owner is responsible for the business aspects of the project, including ensuring the right product is being built, and in the right order. A good product owner can balance competing priorities, is available to the team, and is empowered to make decisions about the product. How are agile projects managed???
  • 10.  The ScrumMaster serves as the team's coach, helping team members work together in the most effective manner possible.  A good ScrumMaster views the role as one of providing a service to the team, removing impediments to progress, facilitating meetings and discussions, and performing typical project management duties such as tracking progress and issues. How are agile projects managed???
  • 11. 1. Satisfy customer through early and continuous delivery. 2. Welcome changing requirements, even late in development. 3. Deliver working software frequently. 4. Business and developers must work together daily. 5. Build projects around motivated individuals. 6. Face-to-face conversation is the most efficient and effective method of collaboration. AGILE PRINCIPLES
  • 12. 7. Working software is the primary measure of progress 8. Agile processes promote sustainable development 9. Continuous attention to technical excellence and good design enhances agility 10. Maximizing the amount of work not done 11. The best results emerge from self-organizing teams 12. At regular intervals, the team reflects and adjusts its behavior accordingly AGILE PRINCIPLES CONT…
  • 13. AGILE METHODOLOGY 1.EXTREME PROGRAMMING(XP)  XP is one of the best known Agile Methodologies. Extreme Programming (XP) concentrates on development of the software enabling the management team to pick the parts of this methodology which work for them.  XP development focuses on release planning and then stages of iteration, where the emphasis is on understanding the “user stories”, leading to user acceptance testing, and to the review and closure of the Iteration with the successful release of the software.
  • 14. AGILE METHODOLOGY 2.SCRUM SCRUM Methodology is another of the well known Agile Processes. "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as opposed to a "traditional, sequential approach“.Scrum uses both managerial and developmental processes.The goal of the SCRUM process is to put out a release. SCRUM Methodology allows for plenty of change during the project.
  • 15.  Lean is another methodology which focuses on maximising customer value and reducing waste.  Agile fits with Lean in that Agile Projects seek to deliver to customer requirements and there is a fit with the quality and continuous improvement of how you work and what that means to your business. AGILE METHODOLOGY 3.LEAN
  • 16. 1.Writing tests before code clarifies the requirements to be implemented. 2.Tests are written as programs rather than data so that they can be executed automatically. The test includes a check that it has executed correctly. 3.All previous and new tests are run automatically when new functionality is added, thus checking that the new functionality has not introduced errors. AGILE METHODOLOGY 4.TEST DRIVEN DEVELOPMENT
  • 17.  Feature Driven Development (FDD) is an iterative software development methodology intended for use by large teams working on a project using object- oriented technology.  The methodology description includes some prescription about what tasks should be done and what roles should be doing them, so many do not consider it a truly agile methodology. AGILE METHODOLOGY 5.FEATURE DRIVEN DEVELOPMENT
  • 18. Managing constraints, scope and quality  Constraints -Managing changes and constraints are one of the essences of Agile management. The way the project is managed will allow the customer to minimize cost of change while taking into account constraints.  Scope –In agile world project, frozen specifications of the final product and abominable snowman are alike: they are both myth and don’t exist in organization dynamics. Rather than defining during the initiation phase the entire project (scope, work breakdown structure, assumptions, etc), the project manager will focus on planning for the horizon.
  • 19. Quality  In agile methodology, quality is planned at the beginning of the project and is continuously present throughout the project lifecycle.  Agile software development put the Quality Assurance in the center of the project management methodology. Because of iterative development and continuous improvement, quality assurance will be involved into the analysis, design and review processes. Managing constraints, scope and quality
  • 20. Values of Agile Project Management 1. Communication is a two way thing. It’s about talking and listening. 2. Simplicity is about simple solutions that do what’s required, no more, no less. Simplicity is synonymous with elegance. 3. Feedback has three axes: Giving feedback, receiving feedback and taking action as a result of the feedback. 4. Courage is about taking calculated risks. It’s about facing and voicing the brutal facts. It’s also about creating an environment where people can be courageous. 5. Respect is an appreciation that everyone can add value. It’s also about valuing diversity.
  • 21. Benefits of Agile 1. Revenue 2. Speed to market 3. Quality 4. Flexibility / agility 5. Right product 6. Visibility 7. Cost control 8. Customer satisfaction 9. Less risk 10.Delivers better systems 11.Responsive to change 12.Delivers greater business value 13.Attractive to the developers 14.More motivating!
  • 22. Problems with agile methods Team members may be unsuited to the intense involvement that characterises agile methods. Prioritising changes can be difficult where there are multiple stakeholders. Maintaining simplicity requires extra work. Contracts may be a problem as with other approaches to iterative development. It can be difficult to keep the interest of customers who are involved in the process.
  • 23. Agile development methodology attempts to provide many opportunities to assess the direction of a project throughout the development lifecycle. By focusing on the repetition of abbreviated work cycles as well as the functional product they yield, agile methodology could be described as “iterative” and “incremental.” In an agile paradigm, every aspect of development requirements, design, etc. is continually revisited throughout the lifecycle. CONCLUSION
  • 24. References   Compuware : Just Enough Agile: Understanding the principles of Agile Development  Zdnet : Agile Project Management Methods for IT Projects