Copyright © 2012 by Mark J. Sebern Sprints Sprint planning Sprint execution.

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

SCRUM basics Julie Rudder & Claire Stewart. What is scrum (Claire) Scrum roles (Claire) Scrum rhythms and processes (Claire) How to write stories (Julie)
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
Copyright © 2012 by Mark J. Sebern Product Owner & ScrumMaster Who are these people, anyway?
Copyright © 2012 by Mark J. Sebern Product Backlog PBI types (extended list) Feature Change Defect Technical improvement Knowledge acquisition Briefly,
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Copyright © by Mark J. Sebern Software Engineering Process I SE Product backlog, estimation, velocity.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Introduction to Scrum.
A Portrait of Scrum Project Management By Nader Khorrami Rad Project Management Professional (PMP) Certified ScrumMaster (CSM) Professional Scrum Master.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Managing a Project Using an Agile Approach and the PMBOK® Guide
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
What is Scrum Process? Where is it used? How is it better?
SWEN 302: AGILE METHODS Roma Klapaukh & Alex Potanin.
Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint Execution.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint review and retrospective.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
SCRUM.
End of Sprint Meetings (Ceremonies)
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Copyright © 2013 by Mark J. Sebern Sprint Review & Retrospective Two “end of sprint” activities Sprint review Sprint retrospective How do they differ?
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
Agile CRM Applying the Scrum Methodology for Deployment Neil Benson.
Created By:-
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Scuola Politecnica Dipartimento DITEN Università degli Studi di Genova An Introduction to Scrum and XP Prof. Riccardo Berta.
Business Intelligence in Classroom WHY:.  Purpose – knowledge to make an informed career decision  Process – Use Scrum method of project management.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Project Management
Scrum.
Scrum and TargetProcess
SCRUM.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
27/05/2018.
Agile Scrum Management
Spring 2013 Advising Starts this week.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
SE 3800 Note 7 Planning, Impediments Ch. 3
SE 3800 Note 7 Planning, Impediments Ch. 3
Creating User Documentation in an Agile World
Microsoft Exam Dumps Questions & Verified Answer - Dumps4downlod.in
CSCE 741 Software Process Lecture 04 Availability
CEN 4010 Intro to Software Engineering Professor Alex Roque
Scrum MODULE 3 – Part 3.
Johanna Rothman Agile Team Measurements Chapter 12
Johanna Rothman Report Your Project State Chapter 14
Scrum Overview.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
CSCE 741 Software Process Lecture 04 Availability
Sprint Planning April 2018.
Introduction to Agile Blue Ocean Workshops.
Scrum: Daily Stand Up Meeting
Agree what we will finish in the sprint
Sprints.
Presentation transcript:

Copyright © 2012 by Mark J. Sebern Sprints Sprint planning Sprint execution

Copyright © 2012 by Mark J. Sebern Sprint Planning What are we trying to accomplish in sprint planning? Goal for the sprint PBI’s aligned with that goal Realistically deliverable in the sprint Plan to complete chosen PBI’s

Copyright © 2012 by Mark J. Sebern Timing When do we do sprint planning? Why then? How long should it take (for a full-time team)?

Copyright © 2012 by Mark J. Sebern Participants Who is involved in sprint planning? Who does what? Product owner Development team ScrumMaster

Copyright © 2012 by Mark J. Sebern Planning Inputs InputDescription Product backlogTopmost PBI’s groomed to Ready state Team velocityIndicator of how much work is practical to complete (units?) ConstraintsBusiness or technical Team capabilities Team member skills and availability Initial sprint goalProduct Owner’s business goal for the sprint

Copyright © 2012 by Mark J. Sebern Planning Approaches Two related activities Choosing what to do Planning how to do it How can these activities be arranged? Choose all items, plan all, repeat till done Choose one item, plan it, repeat till done

Copyright © 2012 by Mark J. Sebern Capacity A measure of the team’s capacity to do work Taking into account “task hours” available Allowing for planning, review, retrospective Don’t forget time off, holidays, etc.

Copyright © 2012 by Mark J. Sebern Measuring Capacity What units? Story points (PBI size) [velocity?] Effort hours (task size) How do we determine team capacity? What adjustments might be needed?

Copyright © 2012 by Mark J. Sebern Selecting PBIs Seems obvious: choose topmost PBIs! But what about the PO’s sprint goal? Why can’t the PO align priorities? Rule: start only what you can finish Why?

Copyright © 2012 by Mark J. Sebern Sanity Check PBIs TasksEffort hours TotalTotal

Copyright © 2012 by Mark J. Sebern Sanity Check PBIs TasksEffort hours TotalTotal What about special skills that some tasks may require?

Copyright © 2012 by Mark J. Sebern Sprint Execution Sprint execution planning Didn’t we just do sprint planning? Flow management Parallel work (multitasking) Swarming Mini-waterfall

Copyright © 2012 by Mark J. Sebern Role-Based Thinking What does the “testing expert” do before there is anything to test? Work together in rapid increments? Develop (by practice during execution) a wider range of team skills? Replace “individual” emphasis with ongoing team collaboration

Copyright © 2012 by Mark J. Sebern Role-Based Thinking What does the “testing expert” do before there is anything to test? Work together in rapid increments? Develop (by practice during execution) wider range of team skills? Replace “individual” emphasis with ongoing team collaboration Using good technical practices is a team responsibility!

Copyright © 2012 by Mark J. Sebern Daily Scrum Daily, 15-minute (time boxed) activity How does this translate to a course project? Don’t forget the three questions! Also: identify “blocking” items that need attention

Copyright © 2012 by Mark J. Sebern In Progress Task Board To DoComplete PBIs

Copyright © 2012 by Mark J. Sebern In Progress Task Board To DoComplete PBIs

Copyright © 2012 by Mark J. Sebern SDL Burndowns What happened here?

Copyright © 2012 by Mark J. Sebern Questions?