|
Embracing Change and Complexity Louis J. Taborda explains that in order to be successful, we need to be able to embrace both change and complexity while being agile. The more quickly we develop software and the greater the sophistication of the solutions we build, the more difficult it is to maintain agility.
|
|
|
Seven Things to Do before Starting an Agile Transformation Where does innovation come from, and how do we get there? Building the next great product may require companies to undergo an agile transformation.
|
|
|
Empowering Agile Teams Teams, when truly empowered, will always make better decisions than any one individual. Where can you empower teams as you adopt agile?
|
|
|
Agile Customer Validation Vision When applying validation, should you limit yourself to the end-of-sprint review or demo—the practice most people associate with agile validation—or should you utilize other validation types where customers provide feedback? Where do the customers who attend validation sessions come from? In this article, you will learn about the importance of the ACVV and how to establish a vision to benefit the product and each project therein.
|
|
|
Four Agile Tips to Eliminate Rework in Application Development Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile.
|
|
|
Experimenting: The Way Forward for Agile Development Teams If you asked anyone on my team what agile practice is most responsible for our success over the past eight years, I bet they'd say retrospectives. But I wonder if it's not so much the retrospectives themselves, as the "small experiments" (to borrow Linda Rising's term) we perform to try to address our problem areas.
|
|
|
Performance Factory for Agile and Lean Organizations Implementing agile and lean performance appraisals presents some unique challenges. This article discusses how to do so in a way that helps to enhance the agile and lean practices that so clearly result in excellent team and organizational performance. The good news is that agile and lean performance management is much more effective than other methods.
|
|
|
An Overview of Lean-Agile Methods Life used to be simpler. In the early 2000s, if you wanted to go "agile," XP was the route of choice. And then Scrum became popular. And it was not too long before organizations began to hit the limits of these approaches due to their focus on teams. And then it became apparent that lean principles could be applied to software and Lean Software Development and later Kanban were added to the mix. Now, you have a great many choices: Not just about which method to use, but where to start, whether to go top-down or bottom-up, and what should be the scope of your effort.
|
|
|
Is Your Agile Audit and Compliance Process Really Agile? In a previous column, George Schlitz proposed that process improvements, such as agile, require organizations to change process rules. Now George continues his review of agile in regards to compliance and auditing practices. What he's found is that changes to compliance and auditing rules may appear compatible, but the implementation process usually remains unchanged and conflicts with agile practices.
|
|
|
Agile Removes Limitations—You Must Now Change the Rules If you're practicing agile methods but continue to reach back to the rules and structures your organization used before adopting agile, you might be asking for more trouble than you know. In this article, George Schlitz discusses the mingling of old and new rules in organizations in different phases of agile adoption and offers a four-step method to help sort out the confusion.
|
|