project management n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Project Management PowerPoint Presentation
Download Presentation
Project Management

Loading in 2 Seconds...

play fullscreen
1 / 85

Project Management - PowerPoint PPT Presentation


  • 118 Views
  • Updated on

Project Management. Quality Management. Getting Started. Things to Consider before getting Started. Management Support Strong and Experienced Leader(s) Picking the right project as a proof point Providing the right education, tooling and governance Ability to allow change to occur

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

Project Management


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. Project Management • Quality Management Getting Started

    2. Things to Consider before getting Started • Management Support • Strong and Experienced Leader(s) • Picking the right project as a proof point • Providing the right education, tooling and governance • Ability to allow change to occur • Keep it Simple

    3. Before Sprints Begin Release Planning: • Product Backlog (Epic User Stories) • Release Themes • Release Backlogs (User Stories) Iteration/Sprint Planning • Sprint Backlog • Information Radiator

    4. Release Planning Form User Story Team to create Product Backlog: • Develop Release Themes • Create Epic User Stories for each release Or: • Create Epic User Stories for Product • Put EUS into releases • Define Release Themes

    5. Release Backlog For Next (or next two) releases: • Break Epic User Stories into User Stories (by User Story Team) • Estimate the Story Points for each user story (by Cross-discipline Scrum Team) • Scrum Team determines “Done, done, done” for each user story

    6. Release Backlog For Next (or next two) releases: • On 3x5 Sticky Notes: • User Story • Acceptance Criteria (record elsewhere) • Business Value (High, Medium, Low) • Differentiating or Parity • Story Points

    7. Release Backlog Prioritize based on: • User stories of highest business value to stakeholders • Risky user stories for development (technology challenges, size of work required, etc.) • Installation • working installer early in cycle allows all teams to move faster • Migration • often difficult to build, and is usually critical to customers

    8. Risk can be an important deciding factor… Avoid Do First Risk Do Last Do Second Business Value

    9. What’s Business Value?

    10. Costs Benefits calculation Value Calculation

    11. Costs Benefits Business Value calculation Value Calculation

    12. Estimate Guess Business Value calculation Value Calculation

    13. Trust any help?

    14. High Market Differentiating Low High Low Mission Critical

    15. High Innovate Market Differentiating Low High Low Mission Critical

    16. High Innovate Market Differentiating Parity Low High Low Mission Critical

    17. High Partner? Innovate Market Differentiating Parity Low High Low Mission Critical

    18. High Partner? Innovate Market Differentiating Who cares? Parity Low High Low Mission Critical

    19. Value Calculation calculation Purpose Business Value Costs and Benefits

    20. other considerations ?

    21. time to market

    22. risks

    23. flexibility Collaboration Model

    24. teamsizeandexperience marketuncertainty domainknowledge teamcapacity technicaluncertainty externaldependencies

    25. Value Calculation Considerations Purpose Costs and Benefits

    26. conversation

    27. resolve differences

    28. group into high – medium - low

    29. For every sprint …

    30. Sprint Planning • Identify a Sprint goal • Select highest priority User Stories from Release Backlog to reach that goal • Product Owner works with scrum team to select user stories from the product backlog for each iteration

    31. Sprint Planning • Team may want to break down stories into: • Smaller User Stories • Or Tasks (all tasks must be done to demo User Story) • Place all sprint stories onto the Information Radiator under Work Planned column

    32. add what to makebetter decisions ? Transaction Costs

    33. at theend of theiteration

    34. now you can ask…

    35. Do we have enough business value to go to market?

    36. Should we continue?

    37. If so, what goes in the next iteration?

    38. Agile Project Management Tips

    39. Key Characteristics of Successful Agile Projects • Short, Stable, Time-Boxed Iterations • Stakeholder Feedback • Self-Directed Teams • Sustainable Pace

    40. Agile Project Management Tips • Expect the teams to over estimate in the first few sprints • It will take about 5 sprints to develop a cadence • Teams make take on too much after some time

    41. Project Management None of us are as smart as all of us. - Japanese Proverb How Do We Deliver?

    42. Leading Agile collaborationmodel • Collaboration Model • Collaboration Process

    43. Project Management • Quality Management create anopenenvironment

    44. fosters creativity and innovation, team commitment and ownership encourages ideas

    45. fosters creativity and innovation, team commitment and ownership encourages ideas what makes it open?

    46. open environment right people

    47. bringthe right peopletogether from theentireenterprise customers marketing sales finance technology manufacturing stakeholders

    48. open environment right people fosterinnovation

    49. Trustworthiness stimulate creativity through collaboration process

    50. open environment right people fosterinnovation step back