BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Techniques Content on InfoQ

  • The Daily Standup/Scrum is not for the Scrum Master

    Mike Cohn recently suggested that the Daily Standup (or Scrum) is not a status meeting for the Scrum Master, but a forum where team members are synchronising their work. Techniques such as breaking eye contact are helpful for Scrum Masters to fix this anti pattern in their teams.

  • Achieving More By Doing One Thing at A Time

    A recent Harvard Business Review article highlights the importance of finishing one task at a time and hence getting more work done. Some of the core Agile practices help minimize context switching and bring a similar task focus while building software.

  • A Collection of Agile Resources by J. Sutherland, K. Schwaber, D. Star, M. Lacey, and D. J. Anderson

    Microsoft has put together a number of resources for Visual Studio developers, containing principles, practices and guidelines for Agile development. These resources are condensed articles written by influential Agile leaders -Jeff Sutherland, Ken Schwaber, David Star, Mitch Lacey, David J. Anderson - containing the essence of several Agile methodologies and being usable by any software dev team.

  • Seven Options for Handling Interruptions on Agile Teams

    Interruptions are something that every team has to deal with and, if not managed appropriately, they can potentially have a detrimental affect on their ability to deliver. In a recent post on the Agile Advice blog, Mishkin Berteig described seven options that teams could consider to deal with interruptions when using Scrum or iterative Agile approaches.

  • Experts advise growing Agile projects with feature teams

    Agile experts suggest a slow ramp up, thinking beyond Scrum of Scums, and using techniques like Feature teams, for scaling Agile projects. A feature team takes responsibility for one or two features at a time and works on them as a whole until they are done. Once the features are delivered, each team member signs up for the next feature by joining another feature team.

  • Product Backlog Ordering, Sequence for Success

    Historically, some product owners have prioritized backlogs by making pairwise comparison of projected economic return between two items in isolation. Successful Agile teams often take a holistic approach, accounting for risk, dependencies, and the complex interplay among and across backlog items.

  • The Agile Community Needs to Embrace... Agile Thought Leaders at YOW! Australia 2011

    What is the most important thing that the Agile community needs to embrace in 2012 and beyond? InfoQ had the opportunity to attend the recent YOW! Australia Software Developer Conference and took the opportunity of having such a large number of Agile speakers in one place to sit in on the sessions and ask them their thoughts on this question.

  • Have the Pragmatists Won? Water-Scrum-Fall Is the Norm

    Dave West, Director of Research and Vice President at Forrester, asserts that Water-Scrum-Fall is the norm in IT today. Forrester's research raises the question: is anyone really doing pure scrum?

  • Agile 2012 Submissions Now Open

    Submissions are now open for the Agile 2012 conference to be held in Dallas, Texas from August 13-17, 2012. Submissions are open until February 19, 2012.

  • Agility Meets Austerity

    As western governments struggle with difficult debt to GDP ratios, the UK is turning to innovation and agile practices to help create a more efficient and less risky IT project delivery framework.

  • Scrum Extensions Update - 4th Quarter 2011

    This is the 4th quarter 2011 update of scrum extensions. InfoQ will be looking at proposed and approved extensions each quarter to see how scrum changes and evolves.

  • Agile 2011 Videos Now Available On New Agile Alliance Learning Center

    The Agile Alliance have recently launched a new Learning Center, with the highlight at launch being the availability of keynotes and selected presentations from the Agile 2011 conference.

  • Should Agile Coaches Have a Code of Ethics?

    Recently on the <a href="http://groups.google.com/group/agile-leaders">Agile Leaders mailing list</a> Dan Mezick initiated a discussion on the need for <a href="http://groups.google.com/group/agile-leaders/browse_thread/thread/23d77a7fd3797ea8">Agile Coaching Ethics</a>.

  • Is Velocity Killing Agile?

    Velocity, the measure of work completed by the team divided by the time taken to complete it, is increasingly being used to manage the productivity of a team and as a comparison between teams. Jim Highsmith, Mark Levison, and Scott Ambler discuss the misuse of velocity as a productivity measure.

  • Can Agile Development Work in Hardware Projects?

    With the take up of Agile approaches in the software world, some commentators in the hardware space have been asking how these techniques can be applied and used in the development of hardware-intensive systems. Two recent articles provide advice and guidance on possible ways to gain the benefits of Agile development in the hardware realm.

BT