It didn't take long for Stacia Viscardi to realize that as effective as agile can be, a plan-driven mindset may not be the best approach for every project or every team. Breaking the rules and embracing whatever it takes to motivate the team to get a project to doneness—and delighting the customer along the way—is a much better approach, even if it means breaking away from fixed iterations.
In this FAQ column, Arlen Bankston defines the roles of Scrum and kanban and describes how the two agile methodologies can be complementary, each ideal for different situations, or blended to achieve the desired outcome.
You read so many books and articles that present how perfectly a Scrum project goes; yet in practice, that is rarely the case. Natalie shares ten lessons that she learned the hard way when she started out as a ScrumMaster. Special attention is given to ways you can avoid those same mistakes.
Whole team testing makes product quality everyone's business. It can also make people uncomfortable. Matt explains how this new way to approach project quality helps with leading retrospectives, conducting defect analysis, and mitigating project risks.
Much like the VCRs of yesteryear, our software development processes are not going to last forever. They’ll fall out of favor, while new and stronger concepts replace them. Jonathan Kohl writes about coping with process evolution in the quest to improve software.
Much like the biblical horsemen of Pestilence, War, Famine, and Death, the "Four Horsemen of the Testing Apocalypse" ride into our lives and work bearing great challenges. If the software of tomorrow is to be better than the software of today, we must face these foes directly.
Whether you’re discussing software defects with your test team, analyzing requirements with your BA, or programming in your favorite new language, communication is essential. Lanette Creamer has some tips to help you communicate clearly with any audience.
We recently sat down with Payson Hall ahead of his upcoming 2012 Better Software Conference East presentation titled "Twelve Risks to Enterprise Software Projects - And What to Do about Them" in order to learn more about his experise in the field of risk management.
In a jazz combo, each member of the team has a specialty. As the members play individually, they create a tapestry of music that becomes much greater than the sum of the individual contributions. A small development team also works best this way.