CSE 201 Chapter Notes - Chapter 4: User Story, Planning Poker, Big Bang
3 Mar 2019
School
Department
Course
Professor
Document Summary
Once it"s time to work, don"t just assign one use story per developer. User stories were for user, describing what software needed to do. Each story is collection of tasks- small bits of functionality that can combine to make up one single user story. Tasks are then carried out by one developer. Have title, rough description, and estimate (planning poker again) Task estimated add confidence by considering the actual coding done. The earlier you can get task estimates, the better. Add task sticky notes to user stories. Only put tasks that are actually being worked on in the in progress section. Board is only as valuable as it is accurate. Two tasks might overlap and it might make sense to tackle them sequentially. Do this when work completed in one task could inform decisions made in the work for another. Don"t double up on tasks with large estimates. Track progress: get everyone"s input on how everything is going.
