#AgileMaxim 1: It is in the doing of the work that we discover the work that we must do. Doing exposes reality.
#AgileMaxim 2: “Responding to Change” is impossible unless code is easy to change, maintain, fix, and enhance, and delete.
#AgileMaxim 3: Question Everything. I focus on my deepest held beliefs. What I trust most hides my biggest problems
#AgileMaxim 4: “Working Software” is software that users are actually using. Until it’s in use it is truly useless.
#AgileMaxim 5: Stress at work diminishes value. Crunch-time is a symptom of harmful and counter-productive attitudes
#AgileMaxim 6: We are the innovators of our process. Learn what works for others, prove it, use it, innovate beyond.
#AgileMaxim 7: The object isn’t to make great software, it’s to be in that wonderful state which makes great software inevitable – Robert Henri, paraphrased
#AgileMaxim 8: The more we work at the work we do, the less capable we become – Make time for improving capability
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I am going through old notebooks and junk to clean up and remove clutter from my house. I have a notebook that includes notes from my first day at Hunter, and my first meeting with the team that 6 months later would stumble upon the idea of #MobProgramming
1/
“My job is to make it possible for you to excel at everything you do here.”
I might rephrase this a bit if I were doing this over again, but it makes me feel good that this is the first thing I said to this team.
It’s a commitment I made to them, and to myself.
2/
That was my first point, and here is a synopsis of the rest of the points I shared:
2- Some things I value
- Respect for our customer, our coworkers, and our team
- Being effective as a team
- “Maximize the whole”
- Continuous improvement
3/
@johncutlefish I’ve managed software development with no estimates. I don’t see how “why estimates” makes sense in that context. #NoEstimates clearly states that I’ve worked without estimates. Like saying “Gluten free” vs “Why gluten?”.
@johncutlefish Or saying “Coke Zero” vs “Why Coke without sugar”. Coke Zero means this drink has #NoSugar. In this context it would be a bit nonsensical to say to say “this drink has Why sugar”. It can have no sugar, or less sugar, or the normal amount, or even extra sugar.
@johncutlefish Once the #NoEstimates hashtag started growing in usage I have used it as marker for a bigger conversation: “Let’s talk about why we do the things we do, with particular attention on the things we do without questioning or verification as to their benefit.”
“Ranged estimates” are an integral part of many processes that use estimates, and have been in use for many decades. However, IMO they’re essentially the same thing as an estimate. 1/
An estimate is typically given as an approximation, as in “it will take about 3 months give or take 2 weeks” 2/
Okay. I didn’t mean to say everyone wants a one size fits all solution - but please understand that many seem to think that it’s that simple.
1/
I’m not proposing that we need an alternative to blink estimation.
If we have a need to make the sort of decisions that blink estimation can try to inform - then there are plenty of techniquesxpeople are using. If they work well, then simply use them.
2/
What I seek is alternatives to the sort things we currently believe is important to decide.
To me, the important consideration, and the discussion that led to the #NoEstimates hashtag, is about why we limit our ourselves to decisions that require estimates.
3/