Development Agile Test & Quality Assurance Project Management Requirements
CM & ALM Devops Cloud Mobile People & Teams

By Topic

Agile Development Methods

Agile Development Stories
Scaling Agile: Reasonable Practices for Program Management

In a big push to scale agile, it can help to think of scaling agile as program management, or coordinating projects where the value is in the overall deliverable. Consider how you can deliver your product one small, finished bit at a time. If you deliver value as often as possible, you see real results.

Johanna Rothman's picture
Johanna Rothman
Just Enough Testing at Each Stage of Your Delivery Pipeline

The continuous delivery pipeline should determine whether the software is a viable candidate for production. Having frequent quality gates along that pipeline that give frequent feedback about the quality of the software helps us find that answer faster. Short feedback loops ensure better product quality.

Gene Gotimer's picture
Gene Gotimer
Are We Sacrificing Quality for the Sake of Speed?

Are we reducing the quality of our code by pushing teams to produce at a speed that might be too fast? Will the final product require multiple updates in order to fix bugs missed along the way? Like just about every question posed about agile, it can depend on the specific team makeup.

Josiah Renaudin's picture
Josiah Renaudin
How to Effectively Transition from Waterfall to Agile

App creation has changed drastically over the past fifteen years, and for many teams, the journey from waterfall to agile has been a challenging one. Sanjay Zalavadia describes three strategies that businesses can use to successfully transition from waterfall to agile processes.

Sanjay Zalavadia's picture
Sanjay Zalavadia
Fail Fast: Embrace Failure to Encourage Success

Fear of failure can hold you back from learning and creating new things. Conversely, creating an environment where it’s safe to fail shows that progress toward mastery is just as important as achieving mastery. A leader who encourages failing fast will have a team where everyone is performing at their best.

Steve Berczuk's picture
Steve Berczuk
Think Agile to Work Efficiently and Effectively

Of course it's important to work efficiently, without wasting time, money, or energy. But working effectively is just as important. Agile cycles between creating, testing, and getting feedback, allowing us to work in small chunks and make sure what we're producing has the most value. That's effective.

Johanna Rothman's picture
Johanna Rothman
Shake Up Your Software Processes: The Intermediate Disturbance Hypothesis

Organizations that refuse to change will get left behind. But at the other end of the spectrum, too much change is also harmful. Revamping everything you do at once creates stress and can lead to your efforts failing. The right balance is shaking things up just often enough to experiment with new ideas.

Matthew Heusser's picture
Matthew Heusser
Scaling Product Agility: More Product, Not More Process

Focusing on scaling product discovery that feeds product delivery is valuable to scaling frameworks. A cross-team product discovery cadence highlights work that's valuable to everyone and facilitates workflow for all the teams, helping them produce more of what they really need (and less of what they don’t).

David Hussman's picture
David Hussman