scrum - How do you make sure that you always have a releasable build? -


how make sure have releasable build?

i'm on scrum team running following problem: @ end of sprint, team presents finished user stories product owner. po typically accept several user stories reject 1 or two. @ point, team no longer has releasable build because build consists of both releasable stories , unreleasable stories , there no simple way tear out unreleasable stories. in addition, not want delete code associated unreleasable stories because typically need add few bug fixes.

how should solve problem? guess there way branch build in such way either (a) each user story on own branch , user story branches can merged or (b) there way of annotating code associated each user story , creating build has working user story. don't know how either (a) or (b). i'm open possibility there easier solutions.

i want stress problem not build broken. build not broken -- there user stories in build cannot released.

we using svn willing switch source control system if solve problem.

in addition answers, i'm interested in books or references address question.

i think desire out incomplete code band-aid on real problem. real problem address doing wrong gets end of sprint unacceptable stories.

sounds me have 1 (or all) of 3 problems.

  1. incomplete conditions of acceptance, apparently don't understand po expects stories done , accepted him. need more work in sprint planning (or before) come understanding of done each story is.

  2. not involving po enough during sprint. demo shouldn't first time has seen stories completed. final ceremony close out sprint. po should have been accepting stories throughout sprint.

  3. overcommitment; if coding last minute don't have time time integrate , test. i'm not sure if meant "bug" in broken-not-tested-code or didn't-work-like-po-wanted-code.

branch per feature expensive thing small teams , more appropriate when building large systems many scrum teams building component parts. it's buying auto insurance because crash lot; doesn't there faster makes pay more along way.

try sprint or 2: don't start on story until po has approved current one.


Comments

Popular posts from this blog

android - Spacing between the stars of a rating bar? -

aspxgridview - Devexpress grid - header filter does not work if column is initially hidden -

c# - How to execute a particular part of code asynchronously in a class -