Multiple Questions
In Daily SCRUM, Development Team should meet every day 15min. Now this statements with take several devs working on the same product? I have two devs each one working on separated products. Since they are 1 on each, how the Daily Scrum will be conducted? Meet anyways two of them?
Second, I have been involved in most of their roadblocks as SM. However, these roadblocks normally block tasks from continuing to reach the Sprint. These roadblocks have mostly to do with accesses (We are working on automation) and we face one rock after other because we rely on client's judgment
SCRUM has to do with an empiric process this gives less chance to junior Developers or Junior SM? If we are starting to work as SCRUM Framework how the empiricism can assist if we have none?
Would you say that the rules in the Scrum Guide are being followed in this case, particularly with respect to team size, composition, and the ability of each team to provide "Done" releasable work every Sprint?
In Daily SCRUM, Development Team should meet every day 15min. Now this statements with take several devs working on the same product? I have two devs each one working on separated products. Since they are 1 on each, how the Daily Scrum will be conducted? Meet anyways two of them?
I agree with Ian on this. If you've only got 2 developers and each work on a different product, you don't really have a team; you have 2 devs working on different products. When you have 2 dev teams, it's best to do the Daily Scrum separate for each team. Otherwise, you're wasting time by having people sit through and listen to stuff that doesn't pertain to them.
Second, I have been involved in most of their roadblocks as SM. However, these roadblocks normally block tasks from continuing to reach the Sprint. These roadblocks have mostly to do with accesses (We are working on automation) and we face one rock after other because we rely on client's judgment
This to me says your PO needs to work closer with your customer to get more detailed information and access before the Dev team begins to work on the items.
SCRUM has to do with an empiric process this gives less chance to junior Developers or Junior SM? If we are starting to work as SCRUM Framework how the empiricism can assist if we have none?
I don't agree that Scrum doesn't have room for junior devs or junior SM's. You have to start somewhere and so long as the goal is to constantly improve and learn, you're incorporating the empirical process; level of competency doesn't matter at that point.
Second, I have been involved in most of their roadblocks as SM. However, these roadblocks normally block tasks from continuing to reach the Sprint. These roadblocks have mostly to do with accesses (We are working on automation) and we face one rock after other because we rely on client's judgment.
Sorry forger question on above. How are the roadblocks managed? US will be back into the Product backlog and as soon as the roadblock is solved Sprint can start?
Also, Sprint cant be longer 4W but can exist multiple Sprints of 2W long? There is not a MAX of Sprints of project correct?
Thank you! Clear now.