Target Process 2.7 has been released. Target Process is an Agile Process Management tool that automates many of the tasks associated with an agile project. Notable features in recent iterations include visual iteration planning, program level release planning, individual velocity reports, and more.
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?
Individuals and interactions over processes and tools is the very first of the values of the Agile Manifesto. Tools, however, seem to be a big part of development on most Agile teams. When does a tool help and when does it hinder (Agile) software development?
"Big Visible Charts" aren't unique to Agile - Lean manufacturing also has its Kanban Boards. "Kanban" roughly means "card or sign," and each Kanban card is "pulled" onto the board only when the work represented by an "in progress" card is retired. In this InfoQ article, Kenji Hiranabe proposes using Kanban Boards to track Agile project status (Time, Task, and Team) to enhance collaboration.
Version One recently announced their new release of V1: Agile Enterprise, InfoQ provide an overview of the new functionality in the latest release of one of the more prominent pieces of Agile project management software.
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.
InfoQ had some time with Mingle project engineer Jay Wallace, to use ThoughtWorks' much anticipated Mingle software and demonstrate to us how it differentiates itself from other products by being a truly agile project management tool.
David Anderson described how his team is using a kanban system for their sustaining engineering (maintenance and bug fixing) activities. Iterations have been dropped although software is still released every two weeks. Work is scheduled, monitored, and run via a "kanban board" and daily stand-up meetings.
Agile methods have achieved a level of success and respect within development teams, but it is not always easy to extend these methods beyond the development team. In Investing in Agile: Aligning Agile with Enterprise Goals, Dan Murphy and Dave Rooney stated that IT project management has evolved with agile methods, but that the enterprise hasn't followed suit.
In a recent newsletter, Scott Ambler looked at why fixed price projects tend to overrun and often fail to solve the business problems they set out to conquer. Scott named the key problems in fixed price projects, identified the bad habits they encourage for customers and developers, and ended with a call to revisit how we fund our IT projects, offering an alternative.
SOA aims at making the entire enterprise agile by using services as the building blocks for applications. Agile software development aims at making organizations agile by introducing practices that increase communication and feedback. This article brought up a few points of agreement and disagreement between the two techniques and readers have started discussion their points of view.
The TargetProcess planning and tracking toolset is evolving quickly. Since release 2.0, they have added Test Cases bound to User Stories and Test Plans, Subversion Integration for requirement-to-source code and defect-to-source code visibility, People Allocation Management and a public Web Services API, making v2.3 a more attractive solution for large Agile shops.
We've all heard the apocryphal stories: "I planned my reno, move, wedding..." using Scrum. Mike Mason of Thoughtworks admitted on his blog: "this whole Agile thing has messed me right up", and shared a picture of his own personal taskboard.
In a recent Datamation article, James Maguire noted the challenge of staying employed in an environment in which the rules are continually rewritten. He spoke with Gartner analyst Diane Morello for 5 predictions for those of us thinking about career directions over the next five years.
In The Freedom of Limited Capacity, Agile coach Mishkin Berteig wrote about what happened when he used Agile planning practices on his own business. By making his long work queue visible, he now had a better way to grapple with reality. Paradoxically, he also experienced a reduction in his stress level - in spite of his very visible backlog! The same effect has been observed on Agile teams.