Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE-2800-06 Product backlog, estimation, velocity.

Slides:

Advertisements

Similar presentations

Iteration Planning.

Advertisements

What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.

Copyright © 2012 by Mark J. Sebern Product Owner & ScrumMaster Who are these people, anyway?

Copyright © 2012 by Mark J. Sebern Technical Debt What is debt (in a financial sense)?

Copyright © 2012 by Mark J. Sebern Product Backlog PBI types (extended list) Feature Change Defect Technical improvement Knowledge acquisition Briefly,

IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.

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.

The Business Analyst Role in Agile Projects

Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.

Practical Story Sizing Brett Maytom Senior Consultant, Readify Vic.NET – 13 Aug 2011.

Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.

Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:

Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?

Agile Methodologies for Project Management By – Komal Mehta.

Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.

Dr. Rob Hasker. Logistics  Class roster, attendance policy  Book, Schedule, policies, grading  Course web site  Prereq check:  SE 2800, Software.

© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.

What is Scrum Process? Where is it used? How is it better?

Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.

SWEN 302: AGILE METHODS Roma Klapaukh & Alex Potanin.

Copyright Robert W. Hasker. Story Review  Elements of a Scrum story:  The three C’s:  Sprintable stories:  Mechanisms for obtaining stories:

Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint Execution.

Release and Iteration Planning September 13, 2008.

©2011 Improving Enterprises, Inc. Epics and Agile Planning.

Copyright © 2012 by Mark J. Sebern Scrum Overview (from

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.

Team Estimation Game Workshop BayXP – October 2007 Estimating User Stories Without Numbers (Well, almost.)

Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.

Dr. Rob Hasker. A new process: YOGA  10 Principles 1. Ignore the past, only look ahead 2. Be artists, free to create 3. Meditate on code each day: what.

Cultivating Agile Requirements

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

Feature-Set (a.k.a. Product Backlog) Management in Scrum

Dr. Rob Hasker Dr. Brad Dennis. Scrum review experience  Lessons learned Saturday Differences from process taught? Similarities? Other lessons?

Copyright © 2013 by Mark J. Sebern Sprint Review & Retrospective Two “end of sprint” activities Sprint review Sprint retrospective How do they differ?

Introduction to Agile. Introduction Who is this guy?

CSE Senior Design II Scrum Review/Discussion Instructor: Mike O’Dell.

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.

Planning 2: Estimation Mechanics Emerson Murphy-Hill Creative Commons Attribution 4.0 License. Material Produced by NCSU Software Engineering Faculty.

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Working Agile in Software Development July-2016 Oracle Confidential – Restricted.

Copyright © Curt Hill Scrum Software Development Paradigms What is a Scrum?

Barnes & Noble Alonda Morgan. Agile UX Agile.

CEN 4010 Intro to Software Engineering Professor Alex Roque

CEN 4010 Intro to Software Engineering Professor Alex Roque

Project Management with VSTS

Agile Scrum Management

Dr. Rob Hasker SE 3800 Note 3 Ch. 4, 5.

SE 3800 Note 7 Planning, Impediments Ch. 3

SE 3800 Note 7 Planning, Impediments Ch. 3

By: By: Agile Scrum Master Online Training.

So You Want to Be a Product Owner

CSCE 741 Software Process Lecture 04 Availability

Johanna Rothman Agile Team Measurements Chapter 12

Scrum Overview.

Definition of Ready.

Scrum - Plan a Sprint Great Video (but added release /sprint layer)

Reporting with Precision and Accuracy

CSCE 741 Software Process Lecture 04 Availability

Sprint Planning April 2018.

Scrum Science NGSS: Engineering, Technology, Applications of Science

Relative sizing.

Speaker’s Name, SAP Month 00, 2017

Software Development In Agile

Presentation transcript:

Copyright © by Mark J. Sebern Software Engineering Process I SE Product backlog, estimation, velocity

Copyright © by Mark J. Sebern Product Backlog Items What are these PBI types?

Copyright © by Mark J. Sebern Product Backlog Characteristics Detailed appropriately Emergent Estimated Prioritized (ordered? positioned?) Estimated size vs position?

Copyright © by Mark J. Sebern Grooming the Backlog Grooming activities Creating/refining, estimating, prioritizing Who makes the decisions? Who else is involved? When is grooming done? How much time to allocate to grooming?

Copyright © by Mark J. Sebern Definition of Ready Ensure top PBI's are "good enough" to take action on (be incorporated into a sprint) What should be included in “good enough”?

Copyright © by Mark J. Sebern Definition of Ready Ensure top PBI's are "good enough" to take action on (be incorporated into a sprint) Business value articulated Details understood Dependencies not blocking Staffing OK Estimated, small enough Clear criteria Acceptance Performance Demo conditions (!)

Copyright © by Mark J. Sebern Ch. 7: Estimation in Scrum Estimation targetSize unit Product backlog item (PBI) Task Story points Ideal hours More on task estimation later...

Copyright © by Mark J. Sebern Estimation Concepts What is meant by these concepts? Estimate as a team Estimates are not commitments Focus on accuracy, not precision Use relative versus absolute sizes

Copyright © by Mark J. Sebern Planning Poker What is this all about? Consensus Expert opinion Discussion Relative size Accurate grouping Use of history How do we play? Why the funny values? 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100, ∞, ?

Copyright © by Mark J. Sebern Velocity What is it? How is it calculated? How do we use the velocity value? For planning? As a diagnostic?

Copyright © by Mark J. Sebern Review Product Backlog Items Item types used at MSOE Characteristics of PBIs: DEEP Grooming, ensuring PBIs are ready Estimation: Planning Poker Velocity

Copyright © by Mark J. Sebern Checkpoint Turn to your partner… What is good about Scrum planning? What seems not so good? What questions do you have?

Copyright © by Mark J. Sebern Estimation Exercise In your team: Choose a PBI to estimate Discuss the item Each estimator privately chooses a card Show all cards at once Check for consensus; repeat if none