Hi Mike: Thanks for an interesting video. I think that planning is fundamental to the success of a project, even though plans don't always work out as we intend them to... think Eisenhower... A method that I think is really helpful is spending time doing two things: splitting stories using the SPIDR method and Story Mapping. Both these techniques help us to deep dive into a project before we start, giving us a good foundation on which to build. Something else that I have started doing also is getting my team to break stories down into two-day increments. That also helps in increasing the accuracy of our time projections/estimates. Thanks for your support and commitment to improving the knowledge and experience of Scrum and Agile practitioners.
@shyamdangi2
4 күн бұрын
Hello Mike - In my one of the projects, we start sprint with almost 60% items spilled over from previous sprint. Testing members have lot of work to complete when its start of sprint and Developers don't have much. In such situations we again pull items which will keep developers busy. But again, at end of sprint we are at the same point where development is done, and more testing items are piled. How can I get rid of this situation.
@MountainGoatSoftware
4 күн бұрын
That can be a tough place to be. The first thing I would suggest doing is to balance out the workload to help get your testers caught up. This means developers help with testing or other tasks once their primary work is done. You should probably also reduce the amount of work that you're bringing into a sprint. If there is consistently 60% rollover then you're overcommitting to the sprint. Try reducing the number of backlog items that you bring in each sprint. After your team is caught up, try having smaller handoffs from programmers to testers. Encourage programmers to avoid finishing entire product backlog items before handing them over to testers. Smaller, more frequent handoffs can help testers start their work earlier in the sprint and help avoid programmers getting far ahead of testers.
@shyamdangi2
3 күн бұрын
@@MountainGoatSoftware Thanks for your reply, Mike. Yes, I have already suggested first option to the team where developers can help testers, however, there seems to be bit reluctant to this as they are not very used to do functional testing. However remaining other option which you have suggested should work. Let me try that way in next sprint.
Пікірлер: 8