13

One of the advantages of having such a small team is that, indeed, the people in the team are able to communicate freely throughout the day. A lot of the daily stand-ups might thus often end very quickly and may look like they are a waste, but they can still have a purpose even in a small team like this: to provide extra focus. The daily standup allows ...


8

The struggle with questions about exams is that for many of these, we don't know what the right answer is. I know which I would pick, but I've read the scrum guide multiple times and can assure you that there is no cannonically correct answer to this questions. So, I am answering with some thoughts to help you understand how I'd get to an answer, but I ...


6

TL;DR Hold the event daily, even if you don't use the whole time box allocated for the meeting. Don't skip it routinely, even if you think you have good reasons. Doing so may not bite you right away, but it probably will eventually. If you're not finding value in the Daily Scrum, it's likely because the team isn't really performing just-in-time (JIT) ...


5

As long as the PO is responsible enough to take the blame if the product fails, it should not be a concern. The project team will be concerned if the PO shoves all the blame on the development and the design teams for a product failure. There will be differences in opinions. When the PO requires something to be done in a certain way, the only way to prevent ...


5

Let Servant-Leadership Be Your Guide The only possible answer of the four is: Allow the Development Team to self-manage and determine for itself what to-do. The other options are all directive and presumptive in nature. Based on the description, it's not even clear that there's an actual problem from the team's perspective, nor that there's a process ...


5

I am trainer myself and I know that it is not helpful to tell right answers straight away. Training is not about learning right answers, but learning for your work life. I will give you right answer to this question and offer to guide you with other questions, that you find the right answer yourself. Coach the team on why the Daily Scrum is important ...


4

You are correct. The Daily Scrum is a meeting for the development team to coordinate the work they will be doing in that day (or more accurately, in the time till the next Daily Scrum). People outside the team (including those in a management role) are allowed to be present in the Daily Scrum, but they are not allowed to interfere or speak up.


4

There are a number of things that might help. First, acceptance can be a continuous process. Could more frequent checking with the PO catch problems earlier? Has the team discussed better approaches to doing the work in retrospective that either lead to less rejections or easier rollback? Also, are stories being rejected and rolled back because they were ...


4

It depends on when your other events are scheduled. The purpose of the Daily Scrum is to coordinate among the team - to inspect progress toward the Sprint Goal and adapt. If you no longer have time to make progress toward the Sprint Goal, why would you need to inspect your progress and adapt your plans to achieving it? Ultimately, I think it depends on ...


4

I've used Scrum in a number of part-time teams and the truth is, nothing really changes - you just have a lower capacity so you plan less work into your sprints. There are only two things I'd consider differently: 1) You have a quarter of the time so I'd expect the meetings to be a quarter of the time. In a 2 week sprint, instead of a 4 hour planning, I'd ...


3

I am part of a majority remote team; and although not part-time, my last project involved a full team of matrixed employees with part-time availability for this project/team. I hope some of my experience will help as you work through the key questions you have listed. Should we try to setup times for when everyone should work, or should we allow ...


3

I would recommend focusing on Agile principles over frameworks (Scrum in this case). GitLab is an entirely remote organisation and don't adopt any specific framework, and instead prioritise Agile principles above any specific framework. If everyone who is working on the project is remote, Strict working hours and meetings/ceremonies will likely inhibit the ...


3

Adding to Daniel's excellent answer... A good way to de-risk merging is to merge frequently in the other direction. For example, the team could use continuous integration to automatically pull code from the head into their feature branch. That way if anyone has introduced code to the head that breaks the branch they will know about it immediately. The ...


3

Answer to your question is: The development team self-manages and is the - only management required at the Daily scrum The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting. Only development team member is allowed to speak/present concern of other members, in ...


3

Testing The job of testing in an agile project falls to all team members. It makes senses to have a dedicated test engineer on the team. But when they start to get overwhelmed with work, other team members, especially developers. It should be part of the code review process to actually checkout and build the changes and test them. This may be a bit more ...


3

The test is almost only represented by a test in the agile team. He is entrusted with all eventualities. From planning, structuring to acceptance test, exploratory testing. The tester criticizes this massive work overload, and that for months in the retro. But there is no solution, or no solution is offered. Thus, the sense behind the retro is not given here....


3

Regarding testing, there is no test role in a scrum team. People may have affinity with testing and might describe themselves as testers, but that does not make them responsible for the test activities. The entire team is responsible that all the needed activities to come to a potentially releasable product are carried out. The PO is supposed to have a ...


2

Here is possibility of both answers: inform management and ask them to solve it. Scrum Master Service to the Development Team according to Scrum Guide: The Scrum Master serves the Development Team in several ways, including: Coaching the Development Team in self-organization and cross-functionality; Helping the Development Team to create high-value ...


2

It is recommended yes. 15 mins of Standup should be doable. When Sprint Planning is scheduled, the team members assemble together either way. Therefore after the Planning is over, the team may just quickly run over the priority tasks and pick a story to work on next.


2

As a Scrum Master I offer my team the option of not having a daily Scrum on the day they do sprint planning. Some teams are happy to skip it and others prefer to stick to the routine.


2

All the other answers contained helpful advices, I have to add some more: Continous integration is used, nightly full automated tests support quality assurance. Every team member has to merge his results at the sprint end to the development branch. This is not continuous integration. In teams I've been working with, "Sprint Branches" turned out to be ...


1

One of the things Scrum does effectively is surface problems, and I believe that's what is going on here: Every team member has to merge his results at the sprint end to the development branch. This isn't a sprint or scrum problem: it's a repository workflow problem. Having developers work on separate branches for days at a time and not merging til they'...


1

TL;DR Helping the team identify the root cause of an issue (to avoid X/Y solutions), and then allowing them to brainstorm measurable solutions that work within the team's unique context is an essential Scrum Master facilitation role. Validated learning and continuous process improvement led by the team should be the real goals here. Analysis For your ...


1

The original question was about an exam and my answer (the accepted one) was geared toward how to consider the answers. You could consider the same things. However, tlyou are going to answer those differently. For example, the purpose of the daily scrum is undermined by less frequent meetings, while it is not undermined but may or may not amplify that ...


1

I'm preparing PSM1, and on my way I found the same question (How is management external to the Scrum Team involved in the Daily Scrum?) in a training exam where i had to select the correct ones (as you can see in the attatched image) and, in the end (once submited the my answers), there was an explanation provided by the people behind the exam. The correct ...


1

A few things to consider: First, let's start with the best: you have super-engaged stakeholders. That is so awesome! And nothing in Scrum says you have to wait until the end of the sprint to show completed work to stakeholders. I don't think it can be overstated how wonderful it is that your team and stakeholders talk frequently! Personally, I wouldn't do ...


1

I would give the following comments to your practice. Daily Scrum: The daily Scrum is a meeting for the team members to discuss if it is possible to reach the sprint goal. In my opinion, there is no space for Stakeholders to review certain user stories. Sprint Review: I wouldn't cancel the meeting. Referred to the Scrum Guide, demo the user stories, ...


1

Is a mid sprint check-in/catch-up a good idea? For the situation you are describing, no. I wonder sometimes do they actually bring up impediments, concerns or issues.  You are worried that people don't bring up impediments or issues at the daily standup. But the meeting you are proposing to have mid sprint has the same purpose as the daily standup ...


1

Firstly, don't worry about "authority". A Scrum Master is a servant leader who achieves things through persuasion, not decree. It's your job to ensure that people and the project are getting value from the ceremonies. The most important meeting in Scrum is the Daily Scrum. If we let that slide, we lose the tightest feedback loop we have. This stand-up ...


Only top voted, non community-wiki answers of a minimum length are eligible