Https://flic.kr/p/hcgHcm Iteration Planning.

Slides:



Advertisements
Similar presentations
System Analysis & Design Methods V Extreme Programming XP/dX.
Advertisements

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.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
User Request BAU Prioritisation process Investment Prioritisation process PM BRD Stakeholders BA BRD Product Backlog Ranked list of requirements from BRD.
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Extreme Programming Mark Steverson. What Is Extreme Programming? ● Extreme Programming (XP) is a lightweight, agile methodology developed by Kent Beck.
Software Configuration Management
Chapter 6 View Alignment Techniques and Method Customization (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Software Development Landscape
What is Scrum Process? Where is it used? How is it better?
Scrum’s Product Owner Role Jeff Patton Agile Product Design
SWEN 302: AGILE METHODS Roma Klapaukh & Alex Potanin.
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
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.
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
5. Planning.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXtreme programming.
Acceptance criteria vs. Functional requirements by Anna Dąbrowska.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
TEST-1 6. Testing & Refactoring. TEST-2 How we create classes? We think about what a class must do We focus on its implementation We write fields We write.
XP Overview Short Life cycle Risky / Dynamic Requirements Increase developer productivity.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
Goals for Presentation Explain the basics of software development methodologies Explain basic XP elements Show the structure of an XP project Give a few.
Extreme Programming Based on and
Lecture 4 – XP and Agile 17/9/15. Plan-driven and agile development Plan-driven development A plan-driven approach to software engineering is based around.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Meeting Practices Yan Wei Foundation Extreme programming is used Meeting practices are based on extreme programming technology with.
Practice Array Web Process By Shengli Hu. Wads Practice 1 review wads everyday morning. mail assignment everyday. keep the status of wads reflect.
Software Engineering 2004 Jyrki Nummenmaa 1 Why new software methodologies The classic waterfall-model based techniques are strongly based on the.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
T Iteration Demo LicenseChecker I2 Iteration
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
Open source development model and methodologies.
Applied Software Testing
Appendix B Agile Methodologies

Monitoring Implementation and Sustainability
Testing Process Roman Yagodka ISS Test Leader.
Project Workflow.
Requirements analysis, representation and validation
Planning User stories are written.
Savannah to Jira Migration
Extreme Programming.
Project management for working professionals
Automated Code Coverage Analysis
Teaching slides Chapter 3.
Teaching slides Chapter 1.
Guidance notes for Project Manager
External Environment Any outside condition that influences the
Chris Rimple Project Expert Team
Sprint Planning April 2018.
Design Team Name Team Members
Planning and Estimation.
Project Planning and Estimation
Teaching slides Chapter 13
Appendix B Agile Methodologies
Extreme Programming.
Planning and Estimation
Iteration Planning.
Project Iterations.
Employee Task Management Software
Review Game.
Planning and Estimation.
Presentation transcript:

https://flic.kr/p/hcgHcm Iteration Planning

Now you have a bunch of user stories with estimates, so what’s next?

Developer Customer Requirements Create USs USs Check USs Corrections/Clarifications Fix USs Add Estimates USs + Estimates Add Priorities USs + Estimates + Priorities Choose USs for Iteration Divide Chosen USs into Tasks Estimate Tasks Assign Tasks to Workers Get to Work!

Principle: Customer sets priorities Ensures alignment with customer goals Helps customer feel in control Project isn’t going “off the rails” Estimates help customer maximize cost-benefit

Priority Numbering Scheme Multiples of 10: 10 - Highest priority 20 30 40 50 … - Lowest priority Non-multiples of 10 may be used if helpful

So now you have… Collection of user stories With estimates And customer priorities What’s next?

Developer Customer Requirements Create USs USs Check USs Corrections/Clarifications Fix USs Add Estimates USs + Estimates Add Priorities USs + Estimates + Priorities Choose USs for Iteration Divide Chosen USs into Tasks Estimate Tasks Assign Tasks to Workers Get to Work!

What’s next… Choose subset of USs to implement this iteration Based on customer priorities Based on time constraints Breakdown subset into tasks More detailed estimates May affect iteration plan Assign people to tasks

From USs to Tasks User Story Estimate

Incremental Development Principle Each task produces running code Unit tests count

Task design strategy Make tasks build upon one another First task makes subset of US work (e.g., partial form) Second task makes bit more work (e.g., add persistence) Etc…

2-Part Activity Part 1: Collect customer priorities Part 2: Assign number each US Also note any corrections/clarifications Part 2: Choose USs for Alpha Iteration 3 weeks worth of work Fill out iteration plan with what each team member will do Everyone codes Tasks must be verifiable and executable Due by start of next class!