|
Agile Testing at Scale
Slideshow
Mary Thorn has had the opportunity in the past twenty years to work at many startups, creating several QA/test departments from scratch. For the past ten years, she has done this in agile software companies. Recently Mary moved from leading small agile test organizations to leading a large...
|
Mary Thorn
|
|
Augmenting Regression Testing in Agile Teams
Slideshow
Today, three things are undeniable facts of business—projects are becoming more agile, teams are learning to function well remotely, and the tester’s role is evolving. Mike Hrycyk believes that testers in agile teams face daunting challenges and often struggle to keep up with the pace of...
|
Mike Hrycyk
|
|
Shift Left Testing: Going Beyond Agile
Slideshow
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation...
|
Michael Nauman
|
|
For Agile to Succeed, Put People First There’s a lot of buzz in the agile world today about becoming more technical, automating everything, and learning the next miracle tool. While it’s important to establish a process, and tools can help with many steps of the software development lifecycle, the human contribution to project delivery is still the most important. Here are some qualities agile teams should encourage.
|
|
|
Are You Agile? An Assessment Can Tell You Plenty of companies want to be agile and go through the motions but are not really agile. An agile assessment allows you to evaluate how teams or even organizations are doing in their agile journey. But like any useful tool, there is no shortage of assessment options available. Here are the acceptance criteria to look for and a framework for using an agile assessment.
|
|
|
How Businesses Stay Agile: The Art of Being Retrospective The greatest use for agile in business is in changing how you tackle problems and projects. Rather than defining the whole project and setting a “way forward,” an agile approach takes things much more iteratively. That means meeting as a team on a frequent and regular basis to share problems and successes, then making improvements as needed—being retrospective.
|
|
|
Streamline Your Agile Requirements by Avoiding Bloated Backlogs In agile development, a bloated backlog results from teams accumulating huge lists of requirements, usually in the form of user stories. Retaining every possible story for building the product weighs down the backlog while squeezing (or obscuring) the highest-value stories. The best way to help minimize this risk is to optimize the time spent defining and refining the product priorities.
|
|
|
10 Things You Must Do to Become Truly Agile Agile is not a state of doing; it’s a state of being. Adopting business models on value and learning how to make teams autonomous are both necessary steps to reap the benefit of agility.
|
|
|
7 Lessons Agile Can Teach Us about Leadership The Agile Manifesto contains values to guide teams toward developing better software. But its directives are also about leadership—influencing culture and creating an organization where people can collaborate to meet the needs of their customers. Here are seven lessons the Agile Manifesto can teach us about leadership.
|
|
|
An Agile Approach to Software Architecture For an organization transitioning to agile development, creating software architecture isn’t incompatible with your new processes. Consider the principles in the Agile Manifesto, involve team members who will be using the architecture in its development, and reflect and adapt often, and you will end up with an architecture that meets the needs of your team and your enterprise.
|
|