Skip to main content

Retro of 2013 Resolution: A Learning Plan

Wish there was an App for That!
As every cycle passes back through the beginning it must first go through the ending... so let's first see if I made any progress in last year's long forgotten new year's resolution.  It was to create a learning plan and bet back into the beginner's shoes.  To become a newbie on some new tech and experience the frustration and excitement of learning a new tech skill.

All in all I did very well.  I did create a learning plan.  And like all plans it was great to have one and worthless after a little bit of learning proved it to be a poor plan (almost like I created it out of ignorance - oh, yeah - I did!).  Yet, it did provide a direction and increased the motivation as I could measure the progress and see where it was directing me in the wrong direction (or a direction I no longer desired to go).

I did learn the basics of RubyMotion (an iOS tool chain - development stack for iPhone apps).
 Ran a few of my example apps on the iPhone simulator.  Never payed to get an Apple developer key and publish my own apps.  I hear that process is quite a learning experience also.  I remember the days of passing the Novell Netware publication standard tests.  A tough code review if there every was one - no memory leak every escaped them - and people wonder why Novell servers could run for decades without reboots.  If you every published a Novell app you don't need to wonder about quality control, you have experienced real QC.  I expect the Apple App-Store is similar, and this aspect of Apples control of the user experience is largely responsible for the happiness of customers.  Windows is known for the blue screen of death, and it is a deserved reputation.   Perhaps human-kind has learned from this mistake so many years ago (1990s).

I would like to take this next step - but I need a team - a group - people to be accountable to - so that I can be my best.  Anyone want to join me - or know of a group I can join?

This is what I've learned about my learning plan - that to be truly successful I've got to enlist collaborators.  This is what Jane McGonigal suggest in her TED talk, it was a key to her recovery from brain injury.  And a key to all great games.  And perhaps a key to life.

See Also:
Review Constraints before Projecting Desires

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: 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
    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."