G.B. SCRUM APP SEASON 4 UPDATE CODE
Then the MicroService03 should be released only with the Epic 04 changes.ĭevTeam03 can handle code branches in following ways. So the Epic 3, and Epic 4 are ready to be go live, but assume Epic 3 is kept hold due to further changes. Task E4T1 -> MicroService03 -> DevTeam03 -> Estimate: 1 day - COMPLETED Task E3T1 -> MicroService03 -> DevTeam03 -> Estimate: 1 day - COMPLETED Task E2T2 -> MicroService04 -> DevTeam04 -> Estimate: 2 weeks - WIP Task E2T1 -> MicroService03 -> DevTeam03 -> Estimate: 1 day - COMPLETED Task E1T3 -> MicroService03 -> DevTeam03 -> Estimate: 2 days - COMPLETED Tast E1T2 -> MicroService02 -> DevTeam02 -> Estimate: 2 weeks - WIP Task E1T1 -> MicroService01 -> DevTeam01 -> Estimate: 1 week - COMPLETED Which means Epic 1 is the highest important one for the end users/customers. Task E4T1 -> MicroService05 -> DevTeam03 -> Estimate: 1 dayĪssume Epic 1, 2, 3 and 4 are ordered by priorities. Task E3T1 -> MicroService03 -> DevTeam03 -> Estimate: 1 day Task E2T2 -> MicroService04 -> DevTeam04 -> Estimate: 2 weeks Task E2T1 -> MicroService03 -> DevTeam03 -> Estimate: 1 day Task E1T3 -> MicroService03 -> DevTeam03 -> Estimate: 2 days Tast E1T2 -> MicroService02 -> DevTeam02 -> Estimate: 2 weeks Task E1T1 -> MicroService01 -> DevTeam01 -> Estimate: 1 week Such CRs/Epics normally get delivered in the next sprint or whenever they are ready.Īssume we have following tasks. When it comes to sub tasks, sometimes there can be tasks which takes more than 1 sprint. Normally a CR getting added as an Epic, each epic can have multiple development tasks for each impacted micro service. Therefore we have lot of internal integrations and dependencies when there are changes. We have huge amount of micro services with multiple dev teams work on each. At each sprint we are delivering "something". We are using agile scrum for our projects and we have 2 weeks sprints.
G.B. SCRUM APP SEASON 4 UPDATE HOW TO
I just want to understand whether this is also practice of Agile, if yes, how to overcome some of the issues mentioned below. Description is too long, but this is a pain point.
0 kommentar(er)
