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

  • 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.

  • Is it Time to Stop Estimating User Stories?

    Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?

  • How Long Would it Take to Build the Product?

    This is one the frequent questions asked by the customer. It is a question that makes an Agile team uncomfortable. On one hand, estimating an entire product functionality without actually starting work is ridden with flaws, however in many circumstances, it is a practical question which teams cannot ignore.

  • Count Bug Fixes Towards Velocity? Depends …

    There have been numerous arguments and debates in the past on whether bug fixes should be counted towards velocity. There does not seem to be a 'one' right answer. However, Agilists have some recommendations describing situations in which they should be added, how they should be added and where they could be avoided.

  • Behavior Driven Development In .NET

    Behavior Driven Development (BDD) is being increasingly seen as an alternative way to approach Test Driven Development. SpecFlow and NSpec are popular frameworks for BDD in .NET. They help create test specifications that are easy to read even for non-programmers and allow the design of the software to be driven by it’s purpose.

BT