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.
Like any great process methodology, agile (and Scrum specifically) can lose sight of the best way to facilitate a development lifecycle from concept to delivery. David Hussman frequently encounters teams that are going through the motions. If your sprint planning meetings have disintegrated into quick listmaking exercises, David will show you how to reinvigorate your team.
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.
It isn't unusual for a project team to believe that adopting a mix of waterfall and Scrum can deliver the best of both worlds. According to Steve, nothing could be further from the truth. In fact, Steve retraces a real project that quickly disintegrated into an absolute disaster.
The software development field has been consumed with process management ranging from inflexible, predictive waterfall all the way to self-governing, adaptable agile approaches. You probably already utilize a specific process methodology on your projects, but have you considered adopting an evolutionary learning cycle process framework instead?
We've all been burned working with software code that, if not designed for long-term maintainability, results in expensive support over a product's lifetime. Kaushal explores three approaches that provide guidelines to ensure that software is designed with maintainability in mind. If you're a software developer, read this!
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.
Without clearly defined roles and responsibilities, actions taken by key project stakeholders may result in project misfires. Kyle shows what you should do to avoid the situation when roles are misunderstood, overlapped, or completely missing.
What do you consider the role of product owner in an agile development project to be? Bob presents a compelling perspective that a product owner has four distinct critical roles that can prove impactful to a team's success.