InfoQ Homepage Scrum Content on InfoQ
-
What Makes a Good Stand Up Meeting?
One of the most simple and yet most talked-about agile practices is the Daily Stand Up Meeting (a.k.a. Scrum). The most recent round of discussions around the subject is occurring right now on the scrumdevelopment Yahoo! group. This discussion has resulted in suggestions about what is important about a Daily Stand Up, how to perform one correctly, and several links to articles on the subject.
-
How Long Should You Sprint For?
What factors influence the length of your sprint? When you're trying to pick a length, between two days and six weeks, what factors should you take into consideration? One coach has taken a stab at identifying shortening and lengthening factors.
-
Don't Worry About Scaling Scrum
Most Scrum adopters have their first doubt in terms of its scalability. Tobias Mayer suggests that before looking into quick solutions for complex problems, adopters should focus on understanding the principles of Scrum. Once the foundation is correctly laid, Scrum will take care of scaling itself.
-
Interview with Joseph Pelrine: Agile Works. But HOW?
Joseph Pelrine has come full circle: from university studies in Psychology, journeying through SmallTalk, XP and Scrum, and now back to broader questions: Why and how does Agile work? In this interview, Joseph talked about Complexity Science, and how story-telling, "sense-making," network analysis and speed-dating's gut-feel approach may prove more useful than our old toolkits for managing teams.
-
Agile Project Management ScrumWorks Pro 3.0 released
Danube Technologies has just released the 3.0 Release of ScrumWorks Pro, last mentioned in August 07. ScrumWorks Pro is an Agile Project Management tool that help track team(s) progress through individual iterations and whole releases. In this release changes focused on two areas: usability improvements and the use of MySQL as the backend database.
-
Is the ScrumMaster-as-Blocker a Pattern to Follow or a Smell to Avoid?
So, you are on a development team that is adopting Agile or thinking of going in that direction. If you are adopting Agile by starting small, you probably are working against-the-grain in your organization. You may have heard that there should be a role that protects the team from the rest of the non-Agile world that might be useful
-
Are Iterations/Sprints Waste or Value to Agile Teams?
Although many people consider iteration to be a key characteristic of agile software development, some question whether or not they're important, and add value to an agile method, or if they're superfluous, or even wasteful. InfoQ has assembled a roundup of arguments on the subject, to help agile teams decide if iterations are important for them.
-
Multiple Projects, One Agile Team
It's not uncommon for an organization to have one group of developers who need to complete multiple projects. In those situations, how should the group be structured, and how should their work be planned and allocated?
-
InfoQ Interview: Jeff Sutherland on "Who's Doing Scrum"
There are over 10,000 Scrum Masters trained, that's a lot of Scrum! Well: Scrum, variants of Scrum, and Scrum-like processes. Are these distinctions important? Jeff Sutherland told us why he thinks it's important to understand a team's level of adoption - not to label it but to continue improvement. He cited the example of organically growing a Scrum team practice-by-practice at Google AdWords.
-
Presentation: Implementing Scrum In A Distributed Software Development Organization
At Agile2007 we heard the tale of a distributed Scrum project with 50 people in 4 continents. BMC Identity Management decided to build their next generation product, including architectural changes and component integration, using Scrum to handle the uncertainty of their product's requirements. This presentation talks about how.
-
ScrumWorks Pro adds Jira, Bugzilla Integration, new Burndown Features
Danube technologies has delivered the Summer '07 release of ScrumWorks Pro, which includes Bugzilla and Jira integration, burndown charts with theme filtering and more options for projecting and trending, as well as other features. InfoQ reports and speaks with Danube technologies.
-
Iteration Types
What is an iteration in the Agile world? How is it different than previous ways the software community has performed iterations? Are there different types of iterations, and does it matter? The ScrumDevelopment list has been recently discussing type A, B, and C sprints (sprint = iteration in Scrum terminology) as defined by Jeff Sutherland and the ideas are relevant the the wider Agile community.
-
InfoQ Interview: Experiences with Planning Poker
In this fourteen-minute interview, Nils Haugen described "Planning Poker," a simple mechanism for arriving at estimates collaboratively, which has additional team building benefits and improves team estimates over time. Haugen shared his views on why this technique is an important tool for Agile teams in this InfoQ interview.
-
Agile Team Size
Using Agile methods with large teams is a reality - the old Agile = Small Team equation is no longer valid. Nonetheless, team size is still an issue. How important is team size and what, if anything, should we do about it?
-
Are Agile Development Practices Detrimental to Architecture and Design?
Is iterative and incremental development à la Agile practices - where one builds only what is required per iteration - detrimental to good design? Does Scrum encourage ignoring architectural issues? Can design and architecture evolve effectively without the technical Agile practices? Does test-first development lead to good design? Or does the red-green-refactor loop stall at local-minima?