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
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.
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 • Keep it Simple
Before Sprints Begin Release Planning: • Product Backlog (Epic User Stories) • Release Themes • Release Backlogs (User Stories) Iteration/Sprint Planning • Sprint Backlog • Information Radiator
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
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
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
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
Risk can be an important deciding factor… Avoid Do First Risk Do Last Do Second Business Value
Costs Benefits calculation Value Calculation
Costs Benefits Business Value calculation Value Calculation
Estimate Guess Business Value calculation Value Calculation
Trust any help?
High Market Differentiating Low High Low Mission Critical
High Innovate Market Differentiating Low High Low Mission Critical
High Innovate Market Differentiating Parity Low High Low Mission Critical
High Partner? Innovate Market Differentiating Parity Low High Low Mission Critical
High Partner? Innovate Market Differentiating Who cares? Parity Low High Low Mission Critical
Value Calculation calculation Purpose Business Value Costs and Benefits
other considerations ?
time to market
flexibility Collaboration Model
teamsizeandexperience marketuncertainty domainknowledge teamcapacity technicaluncertainty externaldependencies
Value Calculation Considerations Purpose Costs and Benefits
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
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
add what to makebetter decisions ? Transaction Costs
at theend of theiteration
Key Characteristics of Successful Agile Projects • Short, Stable, Time-Boxed Iterations • Stakeholder Feedback • Self-Directed Teams • Sustainable Pace
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
Project Management None of us are as smart as all of us. - Japanese Proverb How Do We Deliver?
Leading Agile collaborationmodel • Collaboration Model • Collaboration Process
Project Management • Quality Management create anopenenvironment
fosters creativity and innovation, team commitment and ownership encourages ideas
fosters creativity and innovation, team commitment and ownership encourages ideas what makes it open?
open environment right people
bringthe right peopletogether from theentireenterprise customers marketing sales finance technology manufacturing stakeholders
open environment right people fosterinnovation
Trustworthiness stimulate creativity through collaboration process
open environment right people fosterinnovation step back