1 / 17

Comprehensive Guide to Agile Project Management for IT Projects

Learn key concepts of agile project management, its applicability to IT projects, traditional vs. agile methods, SCRUM, FDD, Crystal Methods, and more. Understand agile manifesto, success criteria, velocity, burndown charts, and resources available. Get insights on roles, testing in agile, and project success criteria.

stevenlowery
Download Presentation

Comprehensive Guide to Agile Project Management for IT Projects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile Project ManagementWaterloo Drupal User GroupMay 2011

  2. Overview • Overview of agile project management • Key concepts and terminology • Available resources and tools • Applicability of agile project management to different types of IT projects

  3. Traditional vs. agile

  4. Waterfall is traditional

  5. Agile methods • SCRUM • Feature Driven Development (FDD) • Crystal Methods • Extreme Programming • Dynamic Systems Development Method (DSDM)

  6. SCRUM is agile

  7. Requirements & features • Can have requirements (e.g., legislative) • Focus is on features (stories, tasks, tests) • Product backlogs consist of features • Features prioritized into releases & sprints

  8. Testing in agile • Product testing can be built into a sprint/iteration • Product testing can be a sprint for a release • User-acceptance testing important • Product issues/bugs addressed daily & by sprint end

  9. Roles

  10. Agile manifesto • Value • Individuals and interactions over processes and tools • Working software [products] over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan Source: Agile Project Management, Second Edition, Jim Highsmith • People & communication = successful projects • Prioritize features & deliver working deliverables early • Focus on what ‘can’ be done within time & budget (positive vs. haggling) • Get feedback regularly and modify scope accordingly

  11. Success criteria In order to work agile projects need: • Co-located teams (collaborative teams) • Daily meetings (daily scrums) • Regular product owner involvement

  12. Velocity and burndown • No Earned Value or baselining • Focus is on velocity & burndown charts • Concept of story points (vs. time estimates) • Velocity: progress calculated by summing up the number of story points completed during a sprint/ iteration • Sprint burndown: Effort remaining vs. date • Project burndown: Points outstanding vs. iteration

  13. Sprint burndown chart

  14. Project burndown chart

  15. Applicability to IT projects • Software development projects • Feature, module, plug-in development • Web application & mobile apps

  16. Resources Online • “Scrum Master in Under 10 Minutes” http://www.youtube.com/watch?v=Q5k7a9YEoUI Books • Agile Project Management: Creating Innovative Products, Second Edition, Jim Highsmith • Managing Agile Projects: The Project Management Essentials Library, Kevin Aguanno Tools • VersionOne Courses • Agile Project Management, Waterloo Centre for Extended Learning

  17. Questions ???

More Related