New answers tagged

0

Scrum's view on the Daily and on Management The 2020 version of the Scrum Guide says this about the Daily Scrum artifact: The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. [...] The Developers can select whatever structure and techniques they want, as ...


0

According to the Scrum Guide, the purpose of the Daily Scrum is to inspect progress towards the Sprint Goal, synchronize activities, and create a plan for the next 24 hours. In a status meeting, individuals give updates on the tasks or items they have each worked on, and there is likely not focus on achieving a valuable business outcome. an effective Daily ...


1

How are these topics different than "I've done work; I am working right now; I am not waiting for anyone"? Where is the collaboration part? You are absolutely right. I have seen enough daily standup where every developer, one after another, answers those three questions. And that, indeed, has nothing to do with collaboration. That is just cargo ...


1

Collaboration at the Daily Scrum Where is the collaboration part? The collaboration is based on the assumption that the Developers are not working in silos, and that they have interdependencies. The purpose of the Daily Scrum is to plan the upcoming daily work cycle. The 2020 Scrum Guide says: The Developers can select whatever structure and techniques ...


1

I think the point about the daily scrum not being a status meeting is that the team shouldn't feel like they are reporting back to the PO, SM, management or other stakeholders at the meeting. It is up to the team to decide how to run their daily scrum. This is the team's time to make sure everyone is properly engaged and the team is productive. The three-...


5

Who, at the Daily Scrum, without changing the attendees, would be receiving the status updates, if it were to be a status meeting? The only required attendees of the Daily Scrum are the Developers on the Scrum Team. Personally, I do find it helpful if the Scrum Master and Product Owner are also there, but that may not be possible in all situations, such as ...


16

The 3 canonical topics are no longer part of the Scrum Guide itself, they were removed in the November 2020 update, because they did indeed allow teams to treat the Daily like a status call. Especially with a manager present (who, by the rules, should not be there or should be an observer only, so if a manager is getting involved, someone should explain the ...


0

Nothing wrong with those 3. The collaboration part is in other things though: I want to talk with you this morning about the alignment What/where is that resource that I could use for ... Is there anyone who can help/explain/give me ... I will leave early today, at .... etc. etc.


1

Refer to the Definition of Done (DoD) and Working Agreements In [S]crum, when do developers typically check their [S]print code into production? There is no prescriptive answer within the Scrum framework, and it's not defined by the 2020 Scrum Guide. Additionally, "delivery" in a Scrum sense is not strictly aligned with the Sprint Review, which ...


1

Adding to the answers you already have... An increasingly common approach is to release code when it is ready, regardless of when that happens in the sprint. The use of feature toggles allows this to happen and means we can separate out 'release to production' from 'release to customers'. So, the general rule is: Release to production behind a toggle when ...


0

Pushing code to production is the latest step in the journey of a code. Here are the steps I use; Developer creates a feature branch on source control related to a story/task Developer pushes code ( including test code ) to the feature branch The "continuous integration" service runs the tests on the feature branch The code is reviewed by peers ...


3

This is going to be highly dependent on the context. I'll start off by saying that "checked into production" doesn't mean anything. Is that "checked into an integration branch in source control" or "checked into the main branch of source control" or "deployed to production"? All of those can be very different things, ...


2

In Scrum, the team's work is represented in two places - the Product Backlog and the Sprint Backlog. The Product Owner is accountable for the management of the Product Backlog. Managing the Product Backlog includes adding and removing items, ordering items, and making sure that the state of the Product Backlog is visible to and understood by all of the ...


0

Get out of the box, there are alternatives to Scrum. Maybe the nature of demand is not the best fit for the Scrum framework. Instead of beating your team to death with workarounds just try to come up with what works for you. For example, in Kanban, you start where you are and improve by small increments. You may end up with a mature Kanban setup, with ...


Top 50 recent answers are included