BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Content on InfoQ

  • Presentation: Planning with a Large Distributed Team

    In this presentation filmed during Agile 2008, Wes Williams and Mike Stout share their recent experience with a large distributed team, the planning hurdles they encountered and how they passed them, and their recommendation: avoid large distributed teams.

  • Presentation: Measuring Agile in the Enterprise: 5 Success Factors for Large-Scale Agile Adoption

    In this presentation filmed during Agile 2008, Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He measures the development progress and effectiveness and compares the results with industry averages. He also presents the factors which contributed to the success of BMC's Agile adoption.

  • Agile Games for Learning

    At Agile 2008, Don McGreal and Michael McCullough ran a session that showed how to use games and exercises to help improve our understanding of Agile principles and practices. After the conference they created the Tasty Cupcakes as a repository for all Agile games.

  • Agility Means Truthfulness

    Talk about agile can often tend toward the tangible things that people do day-to-day, toward the "process of agile", but true agility is really less about process and more about principle. Travis Birch presents his perspective about some of these more intangible aspects of agile, namely "truthfulness".

  • Handling Absence in Scrum Teams

    Absence of a team member whether planned or unplanned can potentially affect the velocity of an Agile team. A discussion on the Scrum Development group tries to find ways to deal with absence.

  • The Power of Done

    Scott Schimanski recently added his voice to those talking about the power of a clear definition of "done." Scott points out there is both business and personal value in a well-defined meaning of "done". The business can count on shipping features that are done, without making any additional investment, while individuals really seem to enjoy the sense of accomplishment that comes with "done."

  • Federal Funding Backs Agile Training in Oregon

    Agile experts James Shore and Diana Larsen will benefit from federal funding to teach two courses in Oregon this month, from Employer Workforce Training Funds and the Oregon Department of Community Colleges and Workforce Development.

  • Presentation: Prioritizing Your Product Backlog

    Choosing the right features can make the difference between the success and failure of a software product. Mike Cohn presented 'Prioritizing your Project Backlog' at Agile 2008 on how a project backlog should be organized and prioritized and non-financial techniques for prioritization such as kano analysis, theme screening/scoring, relative weighting and analytic hierarchy process.

  • ThoughtWorks Announces Twist, Automated Functional Testing Platform

    ThoughtWorks Studios has created Twist, an integrated development environment for functional testing of web and Java applications. The tool provides a single platform for documenting user stories, capturing executable requirements, developing, maintaining, running and reporting on functional tests. A free trial version of Twist is currently available for download and evaluation.

  • What are the Qualities of a Good Test?

    What is a good test? How do we know if we're writing good tests? Kent Beck, Roy Osherove, Mike Hill and others provide some insight.

  • Agile and Offshore: Asking for Trouble?

    Kevin Coleman told his story working with an offshore team that claimed to be 'Agile' and the woes and worries that came with that experience in last month's issue of the Agile Journal. Several readers validated his experience with their own. In practice, can Agile methods be used successfully with offshore teams given today's business reality?

  • Venture Capital Group Acknowledges Overtime Detrimental to Scrum

    Sustainable pace is known to help teams with improved velocity. Jeff Sutherland and Clinton Keith quote studies to prove that it works. However, there is an underlying word of caution which suggests that teams should take their sprint goals seriously and a couple of crunch sprints might not hurt after all.

  • Story-Focused Standups

    A widely accepted agile practice is the daily standup meeting, in which each team member shares: what they have done since the previous standup, what they expect to achieve by the next, and anything that is getting in their way. Mike Cohn recently examined variations that shed additional light on the progress being made toward completing each user story.

  • What is Sprint Zero? Why was it Introduced?

    Some teams use a Sprint 0 to prepare their product backlog, the infrastructure (development environment, CI server), ... .Is this part of Scrum? Is it useful?

  • Presentation: Extremely Short Iterations as a Catalyst for Effective Prioritization of Work

    Mishkin Berteig presents a situation where he proposed to a software development team, which just started to experiment with Scrum, to accept 2-days iterations. The approach was trying to tackle their organizational lack of prioritization resulting in constant crisis. Their decision led to a bigger crisis which exposed the need for task prioritization.

BT