Skip to main content

Leadership Shootout at the Agile2017 corral

Derek "QuikDraw" Lane & I proposed this session (2 sessions actually) for the Agile2017 conference (it wasn't accepted - oh well next time maybe).  Wonder if you'd like to come play in the OK Corral with us?

SlideShare Deck
Here's how it might go down...  Agile2017 Submission # 5835

And if you're interested... comment on this slide deck...  it's not the final answer.  In fact we may be sneaking bigger guns in to the corral under our dusters...

SlideShare deck

Abstract:

Leadership Style Shoot Out :: Which style best works for this context - how will you recognize it?


Where do you Stand

Let's survey the audience's Leadership styles/preferences - we will use a standard reference tool (or maybe just make it up on the fly). Getting the participants up and moving and interacting with each other and the sub-set of leadership styles described on the four flip charts in the corners of the room. We will play a few rounds of the game Constellations. This warm up exercise will most likely bring up some great question on terms and concepts, which we will answer as a group.


Examples of Models & Theories

We will present several models and approaches of Leadership - via Poster Presentations (previous done posters for models of Leadership: Examples: Situational Leadership II, Leader-Member Exchange Theory, Path-Goal Theory, Servant Leadership, etc.) compare and contrast theories of leadership with other leadership approaches: ( Situational, Skills, Style, Trait - also summarized on posters). Gathering insights from participants on experiences with these various leadership styles/traits. Using some famous examples from history and common known examples (JFK, Nixon, Washington, John Wayne, Neil Armstrong, etc).


Review of Literature

We will present a library of books (10 - 30 leadership books) to loan out for the next few days of the conference - participants wishing to come to next session (2 days later) will preform a poster book report on the topics of interest with their small group on the books best topics during the 2nd session. This technique is ripped off from my mentor Sivasailam Thiagarajan (http://www.thiagi.com), I'm sure he will not sue us. This game however is going to require longer than 75 min. to get value - so I'm proposing a radical new idea for conference session - a follow up session scheduled later in the week for the sub-set of participants that choose to participate in this "home-work assignment".

In the 2nd session we will organize the posters - book reviews and give each group/team about 10 min. to present and then a few min. for audience Q&A. Largely dependent on the number of small teams wishing to participate; wishing to go in depth on a topic and learn about that aspect of leadership. Then leave time for a debrief of both sessions.


Information for Program Team:

We are requesting something VERY RADICAL - 2 sessions - for ONE topic - the first session will set the hook: interest a sub set of participants to commit to the second session (the book-review report back poster extravaganza session later in the week).

First session on Monday or Tuesday; second session on Thursday or Friday - link them in the catalog with an "**" and note.

Each session will be independent enough that participant that do not want to attend the other will be carried along with the enthusiastic games of the others that have attended both. Interesting and Learning will be available for all - regardless of attendance of both sessions.


Prerequisite Knowledge:

none really - however we assume many people have been part of a group and have seen many forms of leadership in many different context


Learning Outcomes:

- Awareness of several views of Leadership and Management
- Knowledge of multiple theories of leadership
- develop a lexicon of terms to discuss leadership behaviors
- experience being an emergent leader in a group with a specific objective
- Understanding that styles of leadership change over time throughout history
- Ways to measure effectiveness of leadership (via the fellowship of followers)
- Assessment tools and models to take home and try on your leaders





Post a Comment

Most Popular on Agile Complexification Inverter

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, …

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…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

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 have a problem."

I&#…