Every aspect of product development can be done better or worse. That includes being a team player, writing code, communicating requirements, testing functionality...you name it. But how do you ensure that people do the best thing? And, can you even do that? That is, can you somehow force good practice? And what can you expect to happen by doing so?
Should an agile team begin with requirements documented as use cases or user stories? Proponents from both sides of the debate make good arguments, leading to confusion for many who are just getting started with agile practices.
With over half of companies using a blended agile and waterfall approach to development, it’s critical to be aware of how an agile approach affects planning and alignment with the overall business strategy. Here are the most common challenges in enterprise agile development--and some tips for how smart companies are navigating the new landscape.
Agile project management, and particularly Scrum, can become overwhelmingly consumed by methodology, jargon and rules. This is just the opposite of what was originally intended for agile-lead projects, and it is the communications part of our role that is so important.