Agile Complexification Inverter

 ... no shit, here I am... taking a break from the redundantly recursive link sifting that is iOS development in the 21st Century.  I can not count the stack pushes I've had since about 11 AM and it's only 6:37 PM still time for a beer and a pondering session... A great story allways starts... no shit, there we were... So at my Day Job <euphemism for what I get PAID to do... but I'm unemployeed> I'm writing a little easy App for a colleague - it's a learning chance for me... and it might provide some value.  I'm busily rewiring my brain (there is some question to its inherent plasticity) at my age - so ONE valuable technique is to get drunk enough not to care so damn much and bang out some crap one night - then in the morning come back and fix the hell out of it.  There may be other valuable techniques... Well, last night I decided that the easy array data structure was just going to have to go... that was simple at first and went a long way - but I'd ...

"That went very well."  Said in reference to today's sprint planning session, and an inferred commentary upon the previous planning session which was a tornado disaster zone of a trailer park. Few people like to attend a disaster waiting to happen.  But I've found that there are times when it's the best thing that can happen for a team.  And while I don't cheer for the tornado, I don't mind its visit to the sprint planning meeting once in a while. I'm typically heard explaining why the tornado hit our little trailer park... it's because we didn't do any (or enough) backlog refinement .  And then people want to know what backlog refinement is - what should happen in these "meetings"? If you search the old books and articles on Scrum you might not find this meeting mentioned.  But that's just because refining the backlog was something that most teams understood needed to happen and did what needed to be done.  Somewhere alon...

There are many ways to decompose a large task into smaller portions.  When agilist start doing this there are a few general ways to do such a thing.  Let's start by distinguishing between a story split and a story slice. Splitting != Slicing If you've spent some time with an ax and a pile of wood then you understand that many logs have a naturally easier way to split along with the grain direction.  It requires much less energy to split a log than it does to slice the log. If you've spent some time baking cakes you know that people like to slice cake.  You never hear of a person wanting a split of the cake.  Many cakes have multiple layers, sometimes with different flavors in each layer. What does this have to do with software development stories?  Well many software systems have layers, and it turns out that it is easy to split the layers apart.  For example: the UI layer is easy to separate from the Persistence layer.  Many organizations...

I received this letter from  Jurgen Appelo and thought it might be worth posting here as an example of good criticism and taking action, rather than just complaining.  Yes, there is a  call-to-action   down near the bottom. Dear David, In the Lean-Agile community,  there is a ton of criticism on the topic of certification . Most certificates have little meaning, prove nothing, empty your wallet, and are little more than nasty money-making schemes of savvy certification bodies. At least, that is the sentiment that I usually hear when I bring up the topic. I believe it’s worth trying to do better. 1. Accomplishments One reason for improving upon the idea of certification is that many people find the motivational aspect of certificates to be a positive thing. Human beings crave recognition.  We all want to feel appreciated for the work we do and the successes we have achieved . Badges, awards, trophies, and certificates are standard techniques for signa...

How would you know if your organizations values that you and other leaders have worked so hard to propagate have become weaponized exclusion and status quo control devices? Certainly values are only positive - affirmations of our best selves. Could our values work against us? Yes.  And you may know it only after it is too late... your culture will turn toxic.  The rising stars you spend energy to recruit will say a few months, maybe a year or two and leave (happy to get out).  Or you will force them out within months, because they are not a "good fit" to your culture. This failure to "fit" is a sure sign.  Can the executives read the sign, does you HR department work to protect the status quo?  Hiring decisions use the "good fit" measure and then a few months after they made the mistake of hiring the employee they reverse the decision and fire for "bad fit." As a " journeyman " agilist I've made conscious decision to go into...

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description? An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation. I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_ .  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name. "If the problem has a first name; we are going to hav...

Let's Invert the typically wrong headed view of Software Development project management as a construction project.  We can map it the other way just to see if it works... to have some fun, to explore the meaning of phrases we toss around quite frequently. Site Landing Page Normally Project Management terms come from a construction domain.  We are going to apply the lexicon of modern software to the construction of a home.  We will follow the construction project and meet some of the people doing the work. This is a very small (8 homes from $600,000 skyward) program in my 30-40 year old neighborhood. About 6 months ago I saw the programs landing page go up.  It gives casual observers and some of the stakeholders a general idea of the intent of the program.  And most importantly who to contact for additional information if you happen to be interested in their products. The Refuge program has 8 product projects and has them running independently. ...

by   David Koontz 10 months ago Dialogue on Prerequisites for Collaboration A dialogue on Twitter platform for David's course in IDEO-University's Ideas to Action. An invation to join a Twitter dialogue on the aspects of collaboration. David A. Koontz @davidakoontz Who can help me this afternoon: I'm doing an IDEO-University course on Ideation and Action. 10 MONTHS AGO REPLY RETWEET FAVORITE David A. Koontz @davidakoontz Todays' assignment engage a group of people in brainstorming this activity: 10 MONTHS AGO David A. Koontz @davidakoontz Challenge - what has to happen before collaboration can occur in the workplace? What are some of the situational requirements, 10 MONTHS AGO David A. Koontz @davidakoontz Challenge - and some of the obvious warning signs that might show up when introducing a collaborative activity? 10 MONT...