Skip to main content

On my ToDo book shelf




A wish list of books I'd like to read...

Large-Scale Scrum - more with LeSS  by Craig Larman & Bas Vodde
It describes how we did scrum 10 years ago without the need to think about scaling on a VoIP project at SpeakEasy.  Four teams of around 40 developers (programmers, testers, UI, UX, BA, system engineers, etc.), one backlog, one awesome Product Owner (with a team of help), one deliver of working tested software, on time and on budget.

My current goto resource for how to do Scrum at any scale.





Team Genius: The New Science of High-Performing Organizations
by Rich Karlgaard, Michael S. Malone

"Throughout, Rich Karlgaard and Michael S. Malone share insights and real-life examples gleaned from their careers as journalists, analysts, investors, and globetrotting entrepreneurs, meeting successful teams and team leaders to reveal some "new truths":

The right team size is usually one fewer person than what managers think they need.
The greatest question facing good teams is not how to succeed, but how to die.
Good "chemistry" often makes for the least effective teams.
Cognitive diversity yields the highest performance gains—but only if you understand what it is.
How to find the "bliss point" in team intimacy—and become three times more productive.
How to identify destructive team members before they do harm.
Why small teams are 40 percent more likely to create a successful breakthrough than a solo genius is.
Why groups of 7 (± 2), 150, and 1,500 are magic sizes for teams.


Eye-opening, grounded, and essential, Team Genius is the next big idea to revolutionize business."


Passionate Performance  by Lee J. Colan

This quick read cuts through the clutter to offer practical strategies to engage the minds and heart of your employeees. Learn why this is such a powerful advantage for your organization. Read it and conquer your competition!






Team of Teams: New Rules of Engagement for a Complex World   by General Stanley McChrystal


A NEW APPROACH FOR A NEW WORLD McChrystal and his colleagues discarded a century of conventional wisdom and remade the Task Force, in the midst of a grueling war, into something new: a network that combined extremely transparent communication with decentralized decision-making authority. The walls between silos were torn down. Leaders looked at the best practices of the smallest units and found ways to ex­tend them to thousands of people on three continents, using technology to establish a oneness that would have been impossible even a decade earlier. The Task Force became a “team of teams”—faster, flatter, more flex­ible—and beat back Al Qaeda.
Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

A Beloved Community Fixture

Does your Agile community have a local hub, a place where you are 80% sure you will run into almost everyone in the local universe if you attend enough events, meet ups, and bar tabs?

Mine does, ... let's test this out...  I will tell you my locations - and if you know much about it, let's see if you can ... guess, ... no, not guess,  predict, no... forecast - can you forecast the name of our local hub of Agile community?

I'm in Grapevine, TX ... let me broaden that for you...  Dallas / Fort Worth.

Now if you have any experience with the DFW area ... been to user groups in the area or perhaps software development oriented conferences.... you may know the place where... like Cheers - where everybody knows your name.  Who is it?

Spoilers .... hi sweetie ... I will put the answer a bit further down the page.
I just read this article in INC. - Here's the Secret Sauce for Turning Your Business Into a Beloved Community FixtureBy Leigh Buchanan Editor-at-large, Inc. magazine.

Craftsman - is not the gender neutral term we men believe it to be

Pondering... why are gender "neutral" words such as craftsman are not as gender neutral as we men seem to think they are?
I've been personally trying to break myself from a bad habit... one that I've thought was not such a big  deal...  I use the term "guys" in mixed company to describe a group of people ... not yet a team.  In mentoring groups toward becoming a team, I reserve that term for groups that truly behave like a real team.  I was giving a presentation at a local special interest group and afterwards a person gave me some useful feedback... my usage of the term "guys" was distracting and verging on "off-putting" in the room of mostly females.  I needed to read the audience and the room - and choosing the proper term would help them to engage... what I truly desired.

I remember in the 1970s (yes this should date me) teachers in school told us that some words were considered gender neutral - I believe that "guys" was on…