- The daily scrum meetings are not reported events of tasks, status or to answer the 3 questions (what I did yesterday, what I do today and if I have any impediments), they are meetings to identify impediments and produce actionable plans for that day’s work.
- The daily scrum meetings are not to resolve problems, but to promote quick decision-making.
- The daily scrum meeting should not exceed the 15 minutes of duration. If the team does not talk about all the User Histories (UH) it is because something is bad. To not work in many UHs instantly, focus only on the necessary ones. It Is bad practice to attack many UHs simultaneously.
- The scrum team does not include roles, such as testers, UX/UI, or Technical Leads, because that encourages individual working, not in the product value. The members of the team should find ways to help in areas where they don’t have specialisation, because that is a skill that is expected in the members of the team. For example if there are roles like tester, they could say ‘today I can’t do anything, because I need the release of the developers'. This is an example of bad practice, because you are only focusing on an individual’s work.
- It is false to say that when a team has matured, that it is not necessarily to have a scrum master (SM). A scrum master is part of the team and should always be present.
- The Product Owner (PO) is not accountable for writing the UH or acceptance criteria. The product owner is accountable for the vision, clearing, sorting, final valuation of the product and management of the Product Backlog.
- It is a common problem that developers use a very technical language when talking with other people, but they should talk in terms of the business when dealing with non technical members (ex: PO, SM).
In the scrum, there is no sprint zero, sprint of test, sprint of architecture, sprint of release or sprint of documentation. - If you need non-functional requirements you can add to the Definition of Done (DoD) or to the Product Backlog.
- The DoD normally contains some non-functional requirements like security and levels of quality or performance, which is provided by the Organisation, or ‘if not’ it can be created by the scrum team.
- There is only a DoD, if there are many scrum teams. DoD creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment.
- The DoD can be inspected in the Retrospective Sprint and it can be changed if necessary.
- In the Retrospective Sprint you inspect the last sprint about individuals, relations, interactions, processes, tools and DoD.
- In the Retrospective Sprint the product owner can participate as a member of the Scrum Team.