Plans make us feel safe. And even if they're useful, we'll reach success by getting out of our comfort zone.
Customer collaboration: trust, transparency, communication and shared vision as your best bet against low churn.
Obvious value is obvious: working software over comprehensive documentation
The end of Agile hasn't come series, part 2. I’m one of the first who, in a team, will want to get proper tooling and processes. Why? Especially because once it’s here, I only want to focus on individuals and interactions.
It’s amazing the amount of articles I’ve been reading lately, or the amount of people I’ve heard discussing the same thing: the end of Agile. Seriously?
A backlog is like a garden. At some point, if you don't spend enough time maintaining it, weed will grow. And your Japanese garden will turn into a wasteland.
Product Design is an engineering process. It is not just about drawing a beautiful user interface, it is about building a solution to a user's need. It is a succession of logical steps in thinking and writing, which I recommend to browse through sequentially. And the best approach to my experience is going top down.
Sorry if you're a Product Owner and that you feel you're doing the same than a Product Manager. Either you're actually not, or your company didn't give you the proper job title. And then I strongly encourage you to settle that.
This post is not about Agile. It is about getting things done. And it is about a process that serves business objectives. Understanding your context is key in selecting a methodology, so that you can then embrace it, and finally make it yours. In that specific order.