Cohort Week 7/8

Get Started. It's Free
or sign up with your email address
Cohort Week 7/8 by Mind Map: Cohort Week 7/8

1. Showcase

1.1. Questions wk 7

1.1.1. what did I experiment with in the last week and what did I learn?

1.1.2. what challenges and opportunities are in front of me?

1.1.3. what do I plan to achieve in the next week?

1.2. Questions wk 8

1.2.1. what did I experiment with in the last week and what did I learn?

1.2.2. If you had a squad focused Genie giving you 3 wishes, what would you wish for?

1.2.3. what do I plan to achieve in the next 6 months (IM perspective)?

2. Bits and Roberts wk7

2.1. Laundry List check-in

2.2. IM Cohort vs IM Chapter

2.3. Survey results


2.4. Cynefin

2.4.1. Different problems warrant different decision making approaches Sweet spot of Agile is complex, Lean is complicated Agile makes progress with incomplete information

2.4.2. Different problems warrant different decision making approaches, Cynefin helps you pair the right approach to the corresponding situation Choosing a waterfall approach means you are in a safe complicated domain Often problems have the appearance of complicated when they are really in complex domain (so beware) Analysis paralysis is a tell-tale sign Remember "People will tell you what they want when you have given them what they asked for"

2.4.3. Goal Move around to obvious

2.5. Softed course

2.5.1. Change up retros Actions Visible

2.5.2. Prep time for meetings

2.5.3. POWER purpose outcomes what's in it for them ease engagement roles and responsibilities

2.5.4. Agile not just a process framework/set of practices

2.6. Relative estimation

2.6.1. Why relative? Faster More accurate

2.6.2. T shirt sizing Ideally Squad-iterations as unit of estimation

2.6.3. The people who do the work estimate it No external experts

2.7. Scoreboards

2.7.1. Know what you want to measure and why you want to measure it you need to be committed and passionate to the cause otherwise it won't stick

2.7.2. Lead and lag metrics Lead measures: predictive of goal, influenceable by team

2.7.3. gamification experiment e.g., placing bets on when something will be finished (for other people)

3. B & R wk8

3.1. assignments

3.1.1. Tony

3.1.2. Mike

3.1.3. Sue

3.1.4. Sarah?

3.2. scoreboards

3.2.1. KEY squad engagement! at the moment, it's my baby, I want it to be yours...

3.2.2. transparency of actions

3.2.3. less is more

3.2.4. scoreboard SOP is a comin'

3.2.5. Know what you want to measure and why you want to measure it you need to be committed and passionate to the cause otherwise it won't stick

4. Pomodoro technique/time management/tips for keeping sane


4.2. Self-awareness

4.2.1. fight or flight

4.2.2. feel under pressure (no slack time) -- too many meetings

4.2.3. you and your squad members

4.2.4. => self-regulation our ability to manage our energy states, emotions, behaviour and attention the ability to return to a balanced, calm and constant state of being

4.2.5. Annie Dillard “How we spend our days is, of course, how we spend our lives.” The reason we really care about productivity—or the reason we should care—is that it allows us to do the things we care about as well and effectively as possible Productivity isn’t a goal, but rather a tool for better achieving our goals

4.3. Questions

4.3.1. What is the ONE THING I am committed to completing today? Here’s why it’s beneficial: You train your brain to focus on what is most important You gain a sense of purpose You save yourself time

4.3.2. What are the TWO or THREE things I am committed to completing this week? Under each goal, write down 3 things you would need to do to achieve the desired outcome Devote blocks of time to making progress in the areas Become the master of your time Do an assessment of the progress you made Did some activities take more time than you anticipated? Do you need to plan better? What could you have improved

4.4. Tips

4.4.1. Work on the most mentally challenging tasks in the morning (2 hours after you get up)

4.4.2. Set time slot batches for monkey work, e.g emails, etc

4.4.3. Have regular scheduled “check-in” points during the day

4.4.4. Block out time slots for breaks and focus time Allow slack time

4.4.5. When you focus, use 50 min time slots with 15 min breaks


4.4.7. Find a means to signal "Don't disturb" Go hide Use a sign Remove distractions

5. Poor practices and how to fix them


5.1.1. Stefan Wolpers has a whole bunch of other articles on anti-patterns for different Agile practices/ceremonies

5.2. see 'Bad Smells' slides from these JIT packs

5.2.1. p19 PO JIT

5.2.2. p12 Showcase JIT

5.2.3. p25 IM JIT

5.2.4. p17 IPM JIT

6. Special Request

6.1. Broken Windows theory


7. Iteration Report template