jgs 516 00000111 Key Characteristics (DEEP) § Detailed Appropriately § Emergent § Estimated Size or Effort For stories: a) story points b) ideal days For epics: a) L, XL, XXL ... b) nothing
jgs 516 00000111 Case 1 § Features (Stories) (for this project, almost sure no epics) § Technical Work § Knowledge Acquisition § Defects, not yet (starting the project)
jgs 516 00000111 Case 2 § Features (Stories) (for this project, almost sure no epics) § Technical Work § Knowledge Acquisition § Defects, not yet (starting the project)
jgs 516 00000111 Case 3 § Features (Stories) (for this project, almost sure no epics) § Technical Work § Knowledge Acquisition § Defects, not yet (starting the project) Project O X -
jgs 516 00000111 Case 4 § Features (Stories) (for this project, almost sure no epics) § Technical Work § Knowledge Acquisition § Defects, not yet (starting the project)
jgs 516 00000111 Practice | Case 4 • Can you Define PBIs for these projects • Can you Prioritize the PBIs (1 is highest priority) • Can you Estimate the PBIs with your team (applying Planning Poker) Think carefully about Estimated values. PBI P E
jgs SER 516 Software Agility Javier Gonzalez-Sanchez [email protected] Spring 2021 Disclaimer. These slides can only be used as study material for the class SER516 at ASU. They cannot be distributed or used for another purpose.
javiergs
microcms
naokimrmt
totokit4
yumakann
umizaru
hitokun
ayaka1230
kazumura
heronshoes
mame
headius
akitotsukahara
sachag
malarkey
bkeepers
lemiorhan
productmarketing
davidbonilla
aki_iinuma
rocio
mza
garrettdimon
reverentgeek