Process

Articles

Survival Rules and the Lamp Lighter Survival Rules and the Lamp Lighter

By understanding the context in which their existing practices were meant to work, teams new to agile can more easily decide which of those practices still make sense and which are simply security blankets.

Steve Berczuk's picture Steve Berczuk
Pivot, Pilot, and Adapt Pivot, Pilot, and Adapt

Anupam Kundu and Maneesh Subherwal explain how to operate in a global, hyper-competitive world while avoiding risk-laden experiments and other "stupid" strategies.

Goal, Goal, Who's Got the Goal? Goal, Goal, Who's Got the Goal?

Don Gray explains why software development teams need three common goals: long term, mid term, and short term. These goals focus a team and provide the glue that holds the team together.

Don Gray's picture Don Gray
Celebrating Making the Most of Both Kanban and Lean Startup: Making the Most of Both

Alexei Zheglov reflects on his startup experience and David Anderson’s kanban method in light of Eric Ries’ lean startup movement. Making the most of both approaches requires understanding how they relate to each other.

Alexei Zheglov's picture Alexei Zheglov
Who Is Agile? {Book Review]

Yves Hanoulle has edited a book, called Who Is Agile? I love this book because of all the back-stories, the pictures, and the links. And, oh my goodness, the links.

Johanna Rothman's picture Johanna Rothman
Integrating Games to Change Behaviors, Part 1

Training people and introducing new ideas requires more than just clear, factual explanations or theorems. Brian Bozzuto explores how games, simulations, and other exercises play an instrumental role in helping people be comfortable enough with new ideas that they choose to put them into practice.

Brian  Bozzuto's picture Brian Bozzuto
Agile Lifecycles for Geographically Distributed Teams: A Case Study

In this case study of a distributed agile team, the developers were in Cambridge, MA, the product owners were in San Francisco, the testers were in Bangalore, and the project manager was always flying somewhere, because the project manager was shared among several projects. The developers knew about timeboxed iterations, so they used timeboxes. Senior management had made the decision to fire all the local testers and buy cheaper tester time over the developers’ objections and move the testing to Bangalore.

Johanna Rothman's picture Johanna Rothman
2012: The Year of DevOps

Scott Ambler explains how DevOps has grown within the agile community, and why he believes it will become an IT buzzword in 2012. DevOps uses agile's community-based teamwork and offers developers and those in operations a great way to make everyone's job easier.

Scott W. Ambler's picture Scott W. Ambler
Defining Requirement Types: Traditional vs. Use Cases vs. User Stories

If you have recently transitioned to an agile team, you may have questions about the differences between user stories and use cases, especially how they differ from tradition requirements writing. In this article, Charles Suscheck defines each of these requirements types and uses a running example to illustrate how they differ in a real-world setting.

Charles Suscheck's picture Charles Suscheck
Agile ALM for Delivering Customer Value: Back-end Disciplines

In this second part of a two-part series, Mario Moreira explores the back-end disciplines of a lifecycle that establishes an ALM framework centering on customer value. If your organization has adopted agile and you are looking at building your ALM framework, consider an infrastructure and tooling that will help you establish and build customer value throughout the lifecycle.

Mario  Moreira's picture Mario Moreira

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.