process improvement

Articles

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
How to Give an Accurate Answer

Scott Ames explains the Test Requirements Agile Metric and offers a real-world example of its use in software estimation.

Scott Ames's picture Scott Ames
Updated Agile Program Management Slides Posted

I missed one presentation in my last post. At Oredev, I had an opportunity to speak with the PMI Sweden folks (at least, the southern Sweden folks). I talked about Agile Program Management, and discussed my current thinking about agile program management.

Johanna Rothman's picture Johanna Rothman
Getting to "Done" in Agile Development

When the tasks in the "Done" column needed more attention, the team created a "Done Done" column. Later, they created a "Done Done Done" column. In this article, Brian Bozzuto discusses how you can stop adding columns and honestly get to "done" without having to kid yourself.

Brian  Bozzuto's picture Brian Bozzuto
Early Automation Approach

An early automation approach involves the automation team in the early phase of the testing lifecycle to support agile or iterative projects. Automation scripting can commence in parallel to system development.

Branching to Distraction

Branching can be an effective solution for managing change, enabling parallel development and improved productivity. But, working on a branch is a distraction and can decrease agility, productivity, and code robustness. Learn when the value of working on a branch outweighs the cost.

Steve Berczuk's picture Steve Berczuk
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.

Filip Szymanski's picture Filip Szymanski
Experimenting: The Way Forward for Agile Development Teams

If you asked anyone in my team what agile practice is most responsible for our success over the past eight years, I bet they'd answer "retrospectives". At the start of every two-week sprint, we spend time talking about the previous sprint, identifying areas that need improvement, and thiinking of ways to overcome obstacles. But I wonder if it's not so much the retrospectives themselves, as the small experiments (to borrow Linda Rising's term) we try to address our problem areas.

Lisa Crispin's picture Lisa Crispin
Mission Possible: ScrumMaster and Technical Contributor

Teams trying out Scrum might not be able to justify a full-time ScrumMaster to the organization, so the role is filled by a contributor on the team. This can be a challenge and, if done incorrectly, a problem. Learn some potential issues to be aware of and how to make the hybrid role work.

Steve Berczuk's picture Steve Berczuk
The Competition of Agile

It is sensible to want to avoid the head-butting sort of competition—that is, arguing for the sake of arguing. But, differing opinions and styles can be a good thing. Competitive forces have driven markets, innovation, and civilization for millennia. Here, Jurgen Appelo takes a look at some of the various approaches to agile development and what they bring to the table.

Jurgen Appelo's picture Jurgen Appelo

Pages

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!