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?
Yesterday, I attended the eZ Conference 2015 in NYC as a speaker. As the Product guy at Blackfire.io/SensioLabs, I gave my take on the importance of Continuous Performance Testing.
An article written by Brian de Haaff, CEO at Aha!, about a product management well-known curse.
A recurring joke I hear when teams start using complexity points, and don't fully understand its principles, is their attempts to quantify the stock exchange value of complexity points vs man-hours. Funny, but pointless. Complexity points are part of the Scrum paradigm. Mixing up paradigms is rarely a good idea. Yes Alice, you should follow the white rabbit!
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.