The channel provides informative tutorials on software development using agile. Tutorials covers Scrum, Kanban, and SAFe frameworks.
Tutorials aim to provide practical implementation of agile ceremonies and activities using ALM tools such as Rally, Jira, and TFS.
We aspire to empower development teams by ensuring their SDLC proficiency. To do so, we cover real life and practical challenges and provide solutions using agile framework.
The channel's primary focus is for beginners to thoroughly understand concepts of software development using agile methodology. However, the tutorials should help even experienced team members by refreshing the foundation or get up to speed on SDLC using different tools.
For more information or to book a consulting session, please visit our website agiledigest.com.
Pair Programming isn’t a very common practice in scrum teams but it’s a requirement for “extreme programming”. Most scrum teams don’t do it at all and many scrum developers don’t know how to do it. When people sell scrum on the basis of excellent results they’re often taken from “extreme programming” teams but scrum doesn’t require any technical practices at all which is false advertising.
The biggest problem that prevents me from using this is that it is difficult to find the stories in the sprint you are scheduling work for because the story pane on the right does not have a filter to do this. You can sort by date, and filter by assigned and status etc. but the stories for the sprint you are interested in are lost amongst the other stories.
Any one who have the good knowledge in Scrum Events in the team they can conduct the meetings. There is no such thing call a certain person has to do. If the team agrees then each team member can conduct it day by day.
And my perspective is that if one can write a User story and PO agreed with that User story means. That concern person who wrote the User Story have the full knowledge of the user story and that will help the same person to develop easily.
Yes, Because if the stakeholders are available in the sprint review they know how their product is working. If they feel anything not working according to there plan then they can provide review and team can work according to that.
During IP iteration stage. 7,8 , 9 day every one is involved, What would be doing development team as no iteration or story implementation is being implemented ?
when we say only 4 tickets in dev at a time does it depend upon team size , is there a team size limit for kanban and how many tickets at a given time for say a team size of 10 members ?
Well done!Indeed, a great video to learn and understand. A suggestion: make a practical planning poker session in real team developing software product with POs, BAs, Developers and Scrum Master; purposely to make other understand who it is executed. Nevertheless, I have understood it quiet well, therefore I am contend. Keep posting more video on Scrum related issues.
Product backlog cobtains both refined and unrefined user stories. Sprint backlog contains only refined stories that meet the definition of ready and are being worked on
Are the stories independent of each other in case of workflow splitting? Are they following the Invest criteria, Independent being one of the requirements. Here we cannot complete a story unless other stories are completed. That means we cannot notify customer of price update in cart unless we update it in admin. Correct me if i am wrong.
