Welcome Introductions Agile Traditional Teams Process Delivery Cycle

  • Slides: 25
Download presentation

Welcome & Introductions

Welcome & Introductions

Agile Traditional Teams Process Delivery Cycle: 4 to 6 months Leader: Project Manager Manages

Agile Traditional Teams Process Delivery Cycle: 4 to 6 months Leader: Project Manager Manages delivery of product Delivery Cycle: 2 to 4 weeks Leader: Scrum Master Facilitates process & team dynamics

Shapes Game • Fold the paper in half • Draw a square • In

Shapes Game • Fold the paper in half • Draw a square • In the upper left hand corner draw a circle • At the top of the page draw a triangle • Draw a straight line on the left and right side of the square • Draw a rectangle in the square Done: I will know it when I see it

Agile Manifesto r ways e t t e b g vering o c y

Agile Manifesto r ways e t t e b g vering o c y doin n b u e e r r a a “We g softw do it. n i p o l e of dev lping others he e have w k r o it and this w h g u o r Th value: o t e com Individuals & Interactions Working Software Customer Collaboration Responding to Change Over Processes & Tools Comprehensive Documentation Contract Negotiation Following a Plan in e u l a e is v alue r e h t ev hile w w , , t s h i “That s on the rig ft more. ” le m the ite ms on the ite .

SCRUM Kanban Lean Six Sigma e. Xtreme Programming (XP) TDD Agile Family Tree

SCRUM Kanban Lean Six Sigma e. Xtreme Programming (XP) TDD Agile Family Tree

Paper Airplane Game Your own sub headline Rules Sprint 1 Time: 2 mintues Each

Paper Airplane Game Your own sub headline Rules Sprint 1 Time: 2 mintues Each team will be building paper airplanes Team: 1 designer; can only verbally describe the design, may not build or test 2 builders; can only build they can not test 2 testers; test and accept or reject paper airplane Team Committment: -30 seconds Acceptance Criteria: -Need to look like an airplane -Need to fly 12 feet -Fly relatively staight

Paper Airplane Restrospective Your own sub headline What Worked? What didn’t work and why?

Paper Airplane Restrospective Your own sub headline What Worked? What didn’t work and why? What should we try?

Paper Airplane Game Your own sub headline Rules Sprint 2 Time: 2 mintues Each

Paper Airplane Game Your own sub headline Rules Sprint 2 Time: 2 mintues Each team will be building paper airplanes Team: Self Organized team; the team can define roles Team Committment: -30 seconds Acceptance Criteria: -Need to look like an airplane -Need to fly 12 feet -Fly relatively staight

Paper Airplane Retrospective 2 Your own sub headline What Worked? What didn’t work and

Paper Airplane Retrospective 2 Your own sub headline What Worked? What didn’t work and why? What should we try?

Agile Traditional Teams Process Delivery Cycle: 4 to 6 months Leader: Project Manager Manages

Agile Traditional Teams Process Delivery Cycle: 4 to 6 months Leader: Project Manager Manages delivery of product Delivery Cycle: 2 to 4 weeks Leader: Scrum Master Facilitates process & team dynamics

Scrum Team Release lan Business Vision Technical Vision Process Facilitator

Scrum Team Release lan Business Vision Technical Vision Process Facilitator

Scrum is named for a formation in rugby, which is used to get the

Scrum is named for a formation in rugby, which is used to get the ball moving after it has gone out of play. Players mass together around the ball and with their heads down exert all their power and concentration to get the ball moving. Scrum stuck because of the similarities between the game of rugby and the type of product development prescribed by Scrum.

Scrum Ceremonies Sprint Planning 3 5 8 3 Sprint Backlog (Tasks) q Create UI

Scrum Ceremonies Sprint Planning 3 5 8 3 Sprint Backlog (Tasks) q Create UI (5 hrs) q Code, Unit test validation logic (3 hrs) q User Acceptance Testing (2 hrs) Daily ScrumStandup What did I complete yesterday? What am I working on today? What implements are slowing me down? 2 8 2 13 Sprint ReviewDemo 1 Product Backlog Sprint Retrospective

Scrum Artifacts t! men e r u s a e M up Burn-d own

Scrum Artifacts t! men e r u s a e M up Burn-d own Velocity Trend

Scrum Artifacts Product Backlog

Scrum Artifacts Product Backlog

Scrum: Moving Day To Do: Send s e i t i l Uti t

Scrum: Moving Day To Do: Send s e i t i l Uti t i s o Dep Call s r e v Mo Denotes Impediment Underw Done: ay: k c a P Buy Boxes & Tape

Collaboration Rooms! Copyright© Agile Transformation Inc 21

Collaboration Rooms! Copyright© Agile Transformation Inc 21

Agile Characteristics Daily Standup Copyright© Agile Transformation Inc Business/IS as One 22 C ss

Agile Characteristics Daily Standup Copyright© Agile Transformation Inc Business/IS as One 22 C ss ro F c un t al n io am e T

Agile Key Terms • Work to be done is captured in a list is

Agile Key Terms • Work to be done is captured in a list is called? “Backlog” • A brief statement that describes a piece work that can be executed in a sprint is? “User Story” • Work broken into 2 to 4 week chunks is called? • How much work a team can get done is called the team’s? • Key Scrum meetings are called? • A project’s scope and progress is visually represented by? “Artifacts” • We call the rooms where Agile teams work together? “Collaboration Rooms” • Anything that prevents the team from making progress? “Impediments” “Sprints or Iterations” “Velocity” “Ceremonies”

Questions … Thank You!

Questions … Thank You!