Branching means that you create a new version from the code that exists indepently from the original code. It is not isolated forever, it can be merged back later.
Option C is the way to go. If the developers can't even create a potentially releasable increment, what's the point of all their work? Might as well just hire a magician to make the product appear out of thin air.
Definitely option C! The developers need to have the skills to actually create a working product, not just do the work and leave the deployment to someone else. That's kind of the whole point of Agile, isn't it?
Hmm, I was thinking option B was the right answer. Completing the work on time and within budget is crucial, isn't it? But I guess option C makes more sense in an Agile context.
I agree with Yasuko. Option C seems to be the best answer, as it's important for the developers to be able to deliver a working product, not just complete the work within the given time and costs.
I think option C is the correct answer. The developers should have the skills to create a potentially releasable increment from the product backlog items.
Karan
1 months agoGeorgene
3 days agoKaycee
1 months agoPamela
Herminia
4 days agoCyril
9 days agoTasia
10 days agoJunita
2 months agoRolande
20 days agoTamekia
1 months agoRashida
1 months agoCarlota
2 months agoYasuko
2 months agoNickole
26 days agoHaydee
28 days agoJoanne
29 days agoMarge
1 months agoTori
2 months agoUla
2 months agoLatia
3 months ago