Project Planning and Estimation

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

Indistar® Leadership Team Meetings. Where can we plan a meeting? Choose ‘Plan Your Meeting’ from the main menu screen Click on Meeting Agenda Setup.
Prescriptive Process models
Chapter Extension 16 Agile Development.
Based on the XP Game by Vera Peeters and Pascal Van Cauwenberghe ( 1Software Engineering /Spring.
Some Graph Algorithms.
CS487 Software Engineering Omar Aldawud
Agile Development Chapter Extension 16. ce16-2 Study Questions Q1: Why is the SDLC losing credibility? Q2: What are the principles of agile development.
Agile Planning. The problem with documentation Argument: “Heavy” documentation too much for most business-style projects.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Computer Engineering 203 R Smith Project Tracking 12/ Project Tracking Why do we want to track a project? What is the projects MOV? – Why is tracking.
Customer collaboration.
Customer Collaboration. Central Principles The customer is part of the team The customer plays key role in directing the team 1.
Customer collaboration.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
Project Workflow. How do you do it? -Discussion-
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
Trust-Aware Optimal Crowdsourcing With Budget Constraint Xiangyang Liu 1, He He 2, and John S. Baras 1 1 Institute for Systems Research and Department.
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.
Putting the “Engineering” in Software Engineering: Technology Infrastructure in Process Improvement Adam Kolawa, Ph.D. CEO, Parasoft.
Agile Planning. The problem with documentation Argument: “Heavy” documentation too much for most business-style projects.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
Ms. Bennett. Aim: What can we expect this Spring in Government After School? Do Now:  Explain in three or more sentences why you are here right now.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
SCHOOL AND DISTRICT AGGREGATE REPORTS AGGREGATE REPORTS Where are the reports? What information can be found there?
Evaluation Concepts. Evaluation Concepts Evaluation Concepts Evaluation Evaluation Reporting Reporting Overview.
THE PROBLEM-SOLVING PROCESS BY XITSHEMBISO NICOLLETTE MTHOMBENI G15M
Logical Operators.  Quiz  Let's look at the schedule  Logical Operators 2.
CSE Senior Design II Scrum Review/Discussion Instructor: Mike O’Dell.
Planning Poker-Agile Estimation for Dummies S.INFANTA PRINCY, M.E II YEAR. ANNA UNIVERSITY, TRICHY.
Planning 2: Estimation Mechanics Emerson Murphy-Hill Creative Commons Attribution 4.0 License. Material Produced by NCSU Software Engineering Faculty.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
Getting Started Introducing the Core XP Practices Based on Extreme Software Engineering Daniel H. Steinberg & Daniel W. Palmer.
Project Workflow.
An informal, team oriented, OO design system
Scrum and TargetProcess
Organisation Control KPI’s & an industry Review
Iterative Planning

Individual Thinking Time
Monitoring Implementation and Sustainability
Project Workflow.
Software Requirements
Software Requirements
September 20, 2017 Agile Techniques Workshop Susan Futey
Information Technology Project Management – Fifth Edition
Taking an Iteration Down to Code
EDU 618 Innovative Education- -snaptutorial.com
Johanna Rothman Agile Team Measurements Chapter 12
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
With a partner, We will start our trial presentation on PowerPoint
Coding Concepts (Basics)
<<Project Name>>
Coming up: What is Agile?
Planning and Estimation.
Software Requirements
Log in the System 登入系統 Course Selection System: Choose English version.
Customer collaboration
Extreme Programming.
Iteration Planning.
Planning and Estimation
Iteration Planning.
Software Requirements
Project Iterations.
Planning and Estimation.
Presentation transcript:

Project Planning and Estimation http://flic.kr/p/5wDp8h Project Planning and Estimation

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

Iterative Development Process Requirements Planning Implementation Analysis Design Deployment Testing Evaluation Initial Planning We are here

Developer Customer Create USs Requirements 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!

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!

Principles for Estimation Principle: Past performance is the best indicator of future performance Approach: Track your outcomes; refine your estimates Principle: Wisdom of the crowd Goal: Predict how events will unfold Think event planning Problem: Easy to miss something Solution: More brains = more opportunities to catch eventualities

Principles for Estimation Principle: Past performance is the best indicator of future performance Approach: Track your outcomes; refine your estimates Principle: Wisdom of the crowd Goal: Predict how events will unfold Think event planning Problem: Easy to miss something Solution: More brains = more opportunities to catch eventualities No past performance yet, so…

Estimation with Planning Poker Cards with units of work: 1, 3, 5, 8, 13, 20, 40 Assume team can do 20 units in an iteration For each US: Discuss work involved Flip cards Repeat until consensus Efficiency in estimating is important Don’t expect your estimates to be super accurate

Let’s watch this video to find out what planning poker is all about: http://youtu.be/0FbnCWWg_NY

Some additional estimation principles Give honest estimates that customers can trust Engineers refine estimates; customers refine expectations Estimates are basis for customer’s cost assessment Work at a sustainable pace No heroes, no all-nighters, no super-human feats Either you get the code done like a human being, or you don’t

What’s next… Work on Designs (sitemap, wireframes, model classes) US Estimates