The challenge of knowing whether we are on track to deliver haunts projectmanagers and developmentmanagers at various levels as their organizations take on agile approaches to product and project development. Driving towards smaller work items and lower work in process brings the benefits of both better project risk management as well as more effective agile execution and learning.
Why are some teams successful while others are less than stellar? Can teams use processes to do their work? How can managers help teams to become better? And do we need incentives to improve the quality of software? InfoQ did an interview with Simon Brown about sustainable competence for continuous improvement, balancing people and processes, and software quality and architecture.
Planning and budgeting large projects is often based on trying to predict how development will turn out. Stories are estimated by the development team, but the budget for the whole project is independent from those estimates. Especially for complex projects this leads most often to (unwanted) surprises. Insights from beyond budgeting can help to increase flexibility, and focus on business value.
Eduardo Miranda from Carnegie Mellon University explains planning in agile projects, planning techniques, and the impact of agile on project management offices and the project manager role. 4
"Enterprise Software Delivery" is the latest book by Alan W. Brown, and is a must-read guide for anybody concerned with the development and delivery of software in a large organisation.
Agile projects plan for change, but without clear goals and guidance there is a risk of "solving the wrong problem" - this article discusses the many levels of planning for effective agile project 3
Fixed price contracts are often decried as evil, however they are something which many agile teams face. How can a company execute one using agile practices to achieve better results with lower risk? 15
This article explores things people can do from within their code to make their lives, and the lives of anyone else who has to administer or maintain their application, easier. 5
Agile coach Dave Nicolette looks at: How should we set iteration length? Based on the length of the release cycle? Are there benefits to using shorter iterations? 14
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques. 17
Kenji Hiranabe shows how to track project status using Kanban Boards from three viewpoints (Time, Task, and Team) to enhance self-organization and collaboration. 15
SOA and Agile: Which is right? Which is better? Are we comparing apples and oranges? Can they be used together, and if so, how? This is a discussion topic so come and put in your 2 cents! 22