Plans make us feel safe. And even if they're useful, we'll reach success by getting out of our comfort zone.
Tag: Agile
Customer collaboration
Customer collaboration: trust, transparency, communication and shared vision as your best bet against low churn.
Working software
Obvious value is obvious: working software over comprehensive documentation
Individuals and interactions
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.
The end of the agile world hasn’t come
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?
Continuous Performance Testing: Why you should care
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.
Complexity to assess feasability
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!
Empty your backlog, delete issues
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.
A Top-Down Approach to Product Design in Agile Environment
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.
Why you should care about your Product’s Technical Debt
Products with uncontrolled technical debt are a pain as soon as you want to add or modify even the smallest feature. No matter how good they are, your developers will just struggle in getting your user stories "done".