A little earlier we discuss the Agile Manifesto and the values and the principles of the Agile Manifesto are still part of Scrum. However, Scrum layers on some pillars and transparency is one of the pillars and with transparency the work is all visible to the team and the stakeholders. The status is all visible. Problems are visible, progress is visible and success is visible. Inspection is where the team and the stakeholders look closely at the working solution, make changes if necessary, improve it if necessary, and move it closer to the optimal solution.
The third pillar is adoption. So the business environment is always unpredictable. So always change all of the time, new ways are found, new technologies are discovered. They're used in different ways. Therefore, the team and stakeholders must understand the business environment sometimes, maybe there's suddenly some kind of security vulnerability. The team may have to shift priorities in order to optimize the value that is delivered by the product in the current business environment. And the team and the stakeholders come to consensus on how they should adapt through collaboration. And again, the Agile Manifesto values and principles are still part of Scrum. However Scrum as its own values. One of the Scrum values is courage. So teams have to be willing to ask for help, try new things. Don't be afraid to ask for help, to say that you don't understand something. And also question the status quo and suggest new and better ways of doing things. Focus is another Scrum value. So the team must decline or saying no to work injected from other sources. The team needs to find a core set of activities and focus on them, and get them done. So the whole idea is get the tasks to done. Commitment is a big one. So the team must trust each other. They must commit to completing their work and helping others when help is needed, in order for the team to deliver a working solution increment at the end of every iteration. Respect it's almost a given everywhere, politeness, and kindness. But all members of the team are valuable. All members of the team make their contribution, and all members of the team are needed, in order for the team to deliver.
Finally, openness. Each team member needs to be open about what needs to be done. What's needed to to complete the tasks but also what's needed for improvement. So openness and honesty is given and received by all members of the team.
So again, the values of the Agile Manifesto, they are still there. It's just that the Scrum values are layered on top of the Agile Manifesto values.
Acceptance Test Driven Development (ATDD) involves team members with different perspectives (customer, development, testing) collaborating to write acceptance tests in advance of implementing the corresponding functionality. (see more)
An acceptance test is a formal description of the behavior of a software product, generally expressed as an example or a usage scenario. A number of different notations and approaches have been proposed for such examples or scenarios. In many cases the aim is that it should be possible to automate the execution of such tests by a software tool, either ad-hoc to the development team or off the shelf. (see more)
Antipatterns are common solutions to common problems where the solution is ineffective and may result in undesired consequences. (see more)
In the context of software development, build refers to the process that converts files and other assets under the developers’ responsibility into a software product in its final or consumable form. The build is automated when these steps are repeatable, require no direct human intervention, and can be performed at any time with no information other than what is stored in the source code control repository. (see more)
See product backlog.