|
Making Agile Work for Government: Perceived Challenges to Agile Adoption Erich Knausenberger and Raj Shah examine three perceived challenges to agile adoption in the government space and explore how the "blended approach" to agile adoption offers an effective response to each.
|
|
|
Making Agile Work for Government: A Blended Approach As technology development programs represent some of the biggest line items on agency budgets, there should be little surprise that agile development, with its promise of a fast, lightweight, and iterative approach to delivery of value, has caught the attention of officials from across the government space as they seek to improve their programs’ productivity and effectiveness.
|
|
|
For Programs, Short Is Beautiful Johanna Rothman describes that for programs, since you have many teams, you want shorter iterations and small stories in order to make sure you have as many interconnection points with the rest of the feature teams as possible.
|
|
|
2011 Prediction: Organizations will Continue Applying Agile Strategies at Scale With all of agile's documented successes, the methodologies are being used in areas never before seen. Scott W. Ambler looks into why agile is as popular as it is, and why its popularity will only increase in the future.
|
|
|
Agile ALM—Opposites Attract Agile and ALM are two terms that you don’t often see side by side. To most developers, agile means team interaction, customer collaboration, dynamism, and responsiveness to change. In contrast, ALM seems to imply the opposite of agile, with echoes of rigid procedures, inflexibility, and top-down process control. But are the agile and ALM approaches as contradictory as they first appear to be?
|
|
|
Enterprise Change Management in Agile Software Development Agile software development is designed to thrive within even the most dynamic business and technical environments. All agile methodologies include integrated practices and processes that manage evolving requirements to efficiently develop a continuous stream of new software capabilities. However, what Agile does not address are changes related to enterprise support that falls outside the scope of the project work. Enterprise Change Management (ECM) provides a framework that addresses many of these missing factors.
|
|
|
Enterprise Agile: Yes, Your Whole Company Can Adopt Agile About 12 months ago, our company started an initiative to adopt agile practices across our entire organization—not only our software development organization, but our business organization. For years we had experienced outstanding results by utilizing Scrum for our clients' application development projects. Team productivity improved, executive visibility strengthened, and overall quality increased. Our goal was to capture similar results for our business. Find out how we're doing!
|
|
|
Aligning Agile Efforts with Business Goals A phrase heard often in agile development practices discussions is "let the product lead." Applied correctly, these four words powerfully focus an agile team's energy directly on work that provides the highest business value. Traditional engineering practices that focus on process often divert a technology team's energy away from quick delivery of business value, and toward design of infrastructure and architecture.
|
|
|
Scaling Agile Development via Architecture Every system has an architecture, even systems developed using agile methodologies. Whether you attempt to define that architecture up front in detail or whether it emerges over time is up to you. My experience is that most agile teams follow a strategy somewhere between these two extremes. That strategy, combined with proving your architectural ideas as soon as possible through working code. This article summarizes a collection of strategies for addressing architectural concerns on agile projects and discusses how such strategies can be applied to scale agile methods to large development efforts.
|
|