Friday, June 28, 2019

Why is there resistance to change - mindmap

Courtesy - entrepreneurshipinabox.com, Paycor.com
My Experiences
============

  1. Loss of individual power - Ex PMs now turned into SMs disliked the loss of exercising power in an Agile team. 
  2. Loss or increase of power at org level -- Operations team feared their existence as well as loss of being able to exercise power.
  3. Economic factors -- with reduced manpower, projects / products, and reduced budget, people feared an impact on their perks, forced retirement packages, redundancy packages (if not salaries per se).
  4. Loss of image, prestige, etc.: For program managers, project managers that once had a handle to hire & fire, and in fact be in command about how certain things need to be within the organisation, now found themselves at the mercy of technical teams / organisational change agents, or those designing the organisational teams.
  5. Resource reallocation, realignment, etc.: During early days of org design, squad, chapter, guild formations, there was lack of clarity of specific roles, how existing roles will move over to the new roles, what happens if there is no direct mapping of an existing role with new one, and especially what will be the new R&R (the mandates provided a generic outline of duties), as also how their previous R&R aligned to their contracts with the organisation would change and accommodate their aspirations. In some cases there appeared to be a too steep learning curve for some veterans.
  6. Impact to personal plans


Thursday, June 27, 2019

Handling bugs in Agile - Bradley Bug Chart

Should be this.
  1. Is it a bug? If yes, proceed and fix it first based on priority, else get it into the product backlog.
  2. If it is a bug, can it be deferred to next sprint? If no, proceed below, else move to next sprint. If it is a bug and needs to be addressed in the current sprint, then proceed below.
  3. Can the bug be fixed within 2 hours? If yes, fix it and forget rest.
  4. If no, then get it into the current sprint backlog and remove another item of approx size.


Tuesday, June 25, 2019

Shamrock Mapping - Mike Coon

  1. You may use the Shamrock mapping for retros, or to elaborate on an Element's Dynamics along Autonomy and Mastery.
  2. This is probably derived from Daniel Pink's Drive -- Autonomy, Mastery and Purpose. 
  3. Place an element (as in this case "Compile") along Autonomy - Y Axis, and Mastery - X Axis. 
  4. Then, identify the "accentuators" and "Drags" on both axis. 
  5. Lift are those that allow the element to move to greater autonomy, whereas weight brings it down. 
  6. Likewise, Thrust propels the element along Mastery, while Drag hold it back.


Changing Organisational Culture - Michael Sahota

If we already have automation, what's the need for Agents?

“Automation” and “agent” sound similar — but they solve very different classes of problems. Automation = Fixed Instruction → Fixed Outcome ...