CSE 201 Lecture Notes - Lecture 7: User Story, Planning Poker, Pair Programming
Document Summary
Cse 201 - lecture 7 - user stories, tasks, use cases. Coding may need to break down stories. Tasks: specific piece of development work for 1 developer (or pair programming group). Always best to rely on task estimates. Now user stories have tasks on them with task time estimates. Must only be designated when work is actually started. Your board is only as valuable as it is accurate. Overlap => more work to complete independently. Sometimes working on both is best option. Work completed in one task can inform decisions for another task. More efficient to work on both tasks at same time. Try to double up tasks that are related. Don"t double up on tasks that have large estimates. A meeting so quick there is no need to sit. Use bottom left of big board for unplanned tasks. Estimate the amount of work the new task will take. Explain to customer how it will affect schedule.