From the course: Agile Software Development
Unlock the full course today
Join today to access over 24,800 courses taught by industry experts.
Common myths
From the course: Agile Software Development
Common myths
- Let's wrap up this chapter by discussing a few common myths about Scrum. Let's start with a simple exercise. Look at the following items and identify which ones are required by Scrum. The answer is none of these items are required by Scrum. Scrum is too abstract to require these engineering practices. None of the other items are enforced by Scrum, but many Scrum teams use these techniques as best practices. Perhaps the most common myth about Scrum is that the Daily Scrum is a status meeting. It is just a team hug for the development team. They can conduct the event in whatever way they want. The Scrum Master and Product Owner are not even required to attend the Daily Scrum. Many Scrum teams assume that using software tools makes them agile. Tools assist in the process, but just using tools is not enough. Agility is a mindset and tools cannot make a team agile if the mindset is missing. Another common myth is that agile teams do not document. This myth owes its origin to an incorrect…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
Scrum introduction4m 24s
-
(Locked)
Empiricism3m 6s
-
(Locked)
The scrum pillars (TIA)3m 19s
-
(Locked)
Scrum values1m 54s
-
(Locked)
Scrum roles: The product owner1m 48s
-
(Locked)
Scrum roles: The development team member1m 58s
-
(Locked)
Scrum roles: The scrum master1m 52s
-
(Locked)
Scrum events1m 40s
-
(Locked)
Scrum artifacts: The product backlog3m 43s
-
(Locked)
Scrum artifacts: The sprint backlog and increment1m 47s
-
(Locked)
Common myths2m 28s
-
-
-
-
-