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).
RubyMotion.com
 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: 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, …

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…

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.


Team Performance Model - by Drexler and Sibbet

Many of you have all heard of the Tuckman model of team dynamics (Forming, Storming, Norming, Performing).  It was created in 1966 and has become the most popular model for describing team behavior.  Is it time to level up in your mental model of team dynamics?  Are you ready for a richer more functional model?



Introducing the Team Performance Model by Drexler and Sibbet



Orientation - Why am I here?
"Orientation is about understanding the purpose of a team and assessing what it will mean to be a member.  you need to understand the reason the team exist, what will be expected of you and how you will benefit from membership.  In a new team, these are individual concerns, because the group is only potentially a team.  that is why these concerns are illustrated as occurring in your imagination at an intuitive level.  As a team leader it is important to provide time and space for people to answer these internal questions themselves."

Keys to when Orientation challenges are resolve…

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…