New answers tagged

1

For the sake of argument, ignore for one second the two entry level developers. You now have a team of just the two experienced engineers. Do you see any issues in implementing Scrum now? Probably not. You will develop in sprints, you will have sprint planning, you will do refinement, you will have retrospectives and reviews, build and deploy product ...


2

Who has authority? the designated group leader and Product Owner Here's one of your problems. As a Scrum Master, it's your responsibility to ensure that the Scrum Team (including the Product Owner (PO)) understands and follows the Scrum process. But the PO is your 'designated group leader'. Your boss. You need to clarify expectations from the management ...


2

he thinks the idea of a time-boxed sprint would produce additional stress in the beginning. I disagree with this assessment. The time boxed sprint is not intended to create a stressful deadline. Instead it is a natural break point that allows the team to get feedback and to inspect & adapt. A Scrum team that is a mixture of experienced engineers and ...


1

My answer would be No one, as 'High Priority' work is not a valid reason for changing the WIP during the Sprint. The WIP limit, as in the number of tickets that can be in a particular status of development (a column on the board) is not determined by the urgency of the work but by the amount of work that the team can be working on at the same time ...


Top 50 recent answers are included