InfoQ Homepage Scrum Content on InfoQ
-
How Many Chickens Are Too Many?
The daily scrum is an important meeting within the Agile team. According to Scrum, only the pigs are allowed to speak during such meetings and chickens should just listen. Is there a limit on the maximum number of chickens, who could attend the daily scrums?
-
Scrum Alliance Asks User Group to Sign Licensing Agreement
Today a Scrum User Group closed shop, in response to a Scrum Alliance request "to sign ... a licensing document for a logo they created for Orlando Scrum users group." Community reaction varies widely. Despite clarification from the SA's managing director, it is unclear what, if anything, this trademark application will mean for existing groups.
-
Do Stand-ups Stand Up for Larger Teams?
The daily stand-up meeting helps the team members make a commitment to each other about what they aim to achieve in the day and identify obstacles to progress, if any. However, many Agilists believe that the conventional stand-ups break down quickly as the team size increases.
-
Virtual Panel: Is the Backlog a Vital Artifact and Practice or Waste?
Mary Poppendieck, Ron Jeffries, Jeff Patton, David West, Steve Freeman, and Jason Yip give us their take on backlogs and their importance to successful Agile teams.
-
Don’t Start What Cannot Be Done
Many Agile teams face a dilemma when picking up a new story towards the end of a Sprint. There is some time left but this time may not be enough to get a story done-done.
-
Managers in Scrum
This presentation explores how the role of managers changes in Scrum. It helps managers to lead the introduction of Scrum acting as role models. It presents leadership principles that provide concrete guidance such as servant-leadership, empirical management, empowerment and respect, quality-first and continuous improvement.
-
Are Kanban Workflows Agile?
Karl Scotland started a discussion examining whether the workflows or stages in a kanban system are counter to the agile ideals of cross-functional and collaborative teams. He started by noting that the stages on a kanban board can look a lot like the phases of waterfall. The ensuing discussion clarified that stages are not necessarily hand-offs, and led to other insights as well.
-
Performance Engineering in an Agile Project
Performance Engineering is an important software development discipline that ensures that applications are architect-ed, designed, built and tested for performance. However, mostly in traditional projects the scope of performance engineering is limited to performance testing. This is a sure cause for concern.
-
More on Scrum Certification Test
Mishkin Berteig, a Certified Scrum Trainer, took the Beta CSM Exam on Orlando Scrum Gathering this March, and posted his feedback on Agile Advice.
-
Mapping Traditional Software Development Roles to Scrum
Mapping traditional software development roles to just the three roles in Scrum can be challenging. Mike Cottmeyer attempts to provide an effective mapping which would help the teams.
-
Article: Lean and Agile, Marriage Made in Heaven or Oxymoron?
Dave West takes a look at the world views of the Agile and Lean communities and finds them in conflict. If true, then many of us in the community blending Lean and Agile and unaware of the inherent clash in ideals could be making some big mistakes. As an example of a manifestation of this conflict Dave takes the backlog.
-
Should the Product Owner Be One Person Only?
Is the role of product owner a role that should be satisfied by only one person? There are those who say that there must be one person accountable - a single wringable neck. There are those that say that the expertise needed for a product owner cannot be satisfied by one person. There are many ideas in between about what and who a product owner should be.
-
Adopting The Whole Enchilada
Recently InfoQ reported on Jim Shore's 'The Decline and Fall of Agile', which highlighted a trend for organizations to adopt "Agile" (in name) but fail to adopt what it means to be Agile (in practice). Community leaders such as Joshua Kerievsky, Martin Fowler, and Ron Jeffries have taken Shore's post a few steps further recently, posting their own thoughts on what's going on with this situation.
-
Over-Commitment Versus Over-Delivery
A major goal of sprint planning is to make a commitment to what is intended to be delivered by the end of the sprint. However, many teams either over-commit or over-deliver. Both situations are considered as smells and lead to lack of predictability along with other related pitfalls. The team is required to walk a fine line between the two.
-
Doing Agile After Layoffs
Part of a development team has been laid off, the team is down to four developers with a part time Scrum Master and no dedicated Product Owner. Is Scrum still applicable? What options are there? How does one adapt?