CSE 201 Chapter Notes - Chapter 3: User Story, Diminishing Returns
23 Feb 2019
School
Department
Course
Professor
Document Summary
Every great piece of software starts with a great plan. When they need it, not a moment later. You should let customer choose what user stories are in and which will be cut out to meet deadline. Milestone 1. 0: first major release of software to customer. Don"t get caught planning nice to haves, deliver what"s needed. Don"t worry about length prioritize and don"t get caught up on how long. Customer prioritizes list of user stories and selects those they want to pe part of milestone 1. 0. Sanity-check milestone 1. 0 estimate as reasonable estimate. If the features don"t fit, reprioritize: cut out more functionality: remove user stories that aren"t crucial to software working, ship milestone build as early as possible: this will keep you focused on close deadline, focus on baseline functionality. Every new member must get up to speed on project, understand the software, see technical decisions and how everything fits together. Harder to keep people focused with more people.
