Traditionally our main documentation issue has often been too much documentation – and being done when we have the least information (at the start of the project). Some agile set-ups have started to have the opposite issue – not enough documentation. There are mainly two different ways this can become a problem: insufficient of long-term …
Most professional project managers are actively handling project risks together with the team. And some of those risks are usually related to the product. But in complex product development I would recommend to have rofuces workshop(s) on product risks – where the focus is on everything that can go wrong in the product. You can …
Is the concept of projects dead in agile? Does it matter? In Scrum they say that each sprint can be seen as a project – but that’s not what we normally mean with a project. Personally I don’t really care if we call our development efforts project or not. As long as we make use …
Can traditional Project Control Models (stage-gate, phase-gate or whatever you prefer to call it) work in agile settings? The short answer is yes, but they have to be used in the right way. They are frequently a source of lots of discussions and can also frequently cause a lot of trouble for organizations transitioning to …
Scrum and many Agile Coaches claim that it is of utmost importance to have one Product Owner who makes all product decisions. I can agree that this is the simplest thing that can possibly work in a majority of the situations. It is a good starting point and if it can make sense in the …
There’s already several articles on splitting of User Stories out there, but I have a slightly different approach – and a new acronym that I like to share so bare with me. My advice is to INVEST in good functional splitting and when functional splitting is not enough you use SOUND advice for additional ideas …
What’s the difference between Agile Requirements and traditional requirements (using some broad generalizations)? A couple of key characteristics sets them apart: Format Purpose Timing Sizing Participation Details Priority Change handling Lifespan Format Agile Requirements can be expressed in any format using any tool. Traditional requirements are seen as text and models in documents (electronic or …
