Agile Coach Roles

Get Started. It's Free
or sign up with your email address
Rocket clouds
Agile Coach Roles by Mind Map: Agile Coach Roles

1. As Mentor

1.1. Coaching

1.1.1. Levels

1.1.1.1. indviduals

1.1.1.2. teams

1.1.1.3. Balance of coaching styles

1.1.1.3.1. Focus more on the whole team towards the beginning and end of time-boxes

1.1.1.3.2. Focus more on individual coaching/mentoring in the middle of the time-box

1.1.2. Tone

1.1.2.1. loving

1.1.2.2. compassionate

1.1.2.3. uncompromising

1.2. One 2 One

1.2.1. Condtions

1.2.1.1. Meet folks one half-step ahead

1.2.1.2. Safety

1.2.1.3. Partner with manager

1.2.1.4. +ve regard

1.2.2. Conversation

1.2.2.1. REAL,REAL, REAL

1.2.2.1.1. when conversation is real , changes occur before conversation is over

1.2.2.2. Real conversational is fierce

1.2.2.3. Starting

1.2.2.3.1. for informal conversation

1.2.2.3.2. observation vs invitation

1.2.2.4. Middle conversation

1.2.2.4.1. use powerful question

1.2.2.4.2. I have to revise the paper "The Art and Architecture of Powerful Questions" http://www.javeriana.edu.co/decisiones/PowerfulQuestions.PDF, I read it before but i need to read it deeply these days

1.2.2.4.3. No problem solving

1.2.2.5. End conversation

1.2.2.5.1. accountability

1.2.2.5.2. keep it peer level but coach have few skills more

1.2.2.5.3. personally , I have that feeling that all humans are similar and I am just lucky because God want me to have this level of education and knowledge

1.2.2.6. coach limits

1.2.2.6.1. it is agile coach not career coaching , do not let it go career coaching

1.2.2.6.2. No expert opinion

1.2.2.7. Subject Matter expertise

1.2.2.7.1. It is mentioned that coach is not supposed to be subject matter which I do agree totally for , however, I think it is important for coach to have little domain knowledge that allows him to follow the conversation between team members and understand the blocking issue .personally I was really offended when dealt with PM who have no any technical experiences to the limit they do not understand the problems we have in development team

1.2.2.8. I think having some one (Agile coach ) responsible only for taking care of every team members is really great and can push the whole team forward a lot

1.3. Coaching Product Owners

1.3.1. focus on business value delivery

1.3.2. product owner roles

1.3.2.1. business value driver

1.3.2.2. vision keeper

1.3.2.3. daily decision maker

1.3.2.4. heat shield

1.3.2.5. ultimately responsible

1.3.3. "giving feedback to product owner may be daunting task "

1.3.3.1. based on the character of the product owner it way be daunting or not . for product owner i dealt with before i would say: "Huh ! what a challenge??!!"

1.3.3.1.1. what hard person , he is always keen to achieve the best for his product so if he found something he thinks it will really improve his product he will accept

1.3.3.1.2. owner is willing to comply with the company polices (like applying good agile practices )

1.3.3.1.3. I must keep in my mind he is really in need for that and if he just got the point he will take it for sure

1.3.4. Business value micro definition

1.3.4.1. Does [xxxx] ramp up users?

1.3.4.2. does [xxxx] get channel partner ready ?

1.3.5. some cases of owners

1.3.5.1. this are some area of improvement that I should search for and tackle if exists

1.3.5.2. owner do not do process

1.3.5.3. owner do not know how to frame releases

1.3.5.4. do not know how to find real customer needs

1.3.6. Business value system

1.3.6.1. buiness value is combination of

1.3.6.1.1. value

1.3.6.1.2. cost

1.3.6.1.3. risk

1.3.6.1.4. knowledge

1.3.6.2. owner must give priority for items with highest business value

1.3.6.2.1. having blockers is not justification for not putting items with high business value on top priories .I believe that i can really use this skills with my customers and this make my customer have feeling of satisfaction although i am not delivering all contract items

1.3.6.3. product owner MUST MUST face the value restricting blockers

1.3.7. being good for team

1.3.7.1. agile coach can not make up for poor product owner

1.3.8. values for product owner

1.3.8.1. these values must be communicated clearly for product owner and monitored continuously. I can make mugs or other gifts with these values printed on it so product owner can see it contiguously

1.4. Coaching Agile Coaches

1.4.1. i believe this section is not only useful when i want to train coach but it is important to let scrum leads acquire small set of coaching skills in order to handle diffident situation . it also important to for their personal feeling

1.5. Coaching Agile Managers

1.5.1. Role

1.5.1.1. Manage teams

1.5.1.2. Manage investment

1.5.1.3. Manage environment

2. As Facilitator

2.1. On important resource for me about facilitation skills is PeerEducationTrainingof TrainersManual , I would call it a theory in action book , it discusses how to make training for facilitators in a step by step practical approaches with support of many theories which is explained in simple and relevent way

2.2. About Facilitation

2.2.1. helping them get better

2.2.2. It is about providing container for team to put their idea.

2.2.2.1. that's why wikipedia is wikipedia ? such approach can really make miracles

2.2.3. It is for formal and informal conversations not formal only.

2.3. Stand-Up facilitation

2.3.1. 3 question ; What did you do yesterday ? What will you do today ? Do you have any blockers ?

2.3.2. Why? Values ? Objectives of stand-up

2.3.2.1. these objective has to be in my mind id i was asked "what stand-up everyday ?" 5 values

2.3.2.2. Peer pressure

2.3.2.3. Fine-grain Organisation

2.3.2.4. Focusing on few

2.3.2.5. Daily commitment

2.3.2.6. Raising impediments

2.3.3. How?

2.3.3.1. 15 min

2.3.3.2. 3 questions

2.3.3.3. no long conversation

2.3.3.4. I would add also for the new teams "the 5 values of Stand-Up". Many people Know Stand-ups is useful but few people has clear understanding why is it useful .

2.3.3.5. You may offer observation afterward

2.3.4. Fixing Stand-Up

2.3.4.1. When to fix it ?

2.3.4.1.1. for new agile teams , model positive Stand-Up directly

2.3.4.1.2. On established teams , choose to intervene of not

2.3.4.2. How?

2.3.4.2.1. Reinforce the purpose of Stand-Up

2.3.4.2.2. Ask for eyes and Support.

2.3.4.2.3. One 2 One coaching

2.3.4.3. If intervention failed?

2.3.4.3.1. Lets them pay the consequences

2.3.4.3.2. Do not leave these moment slip by

2.3.4.3.3. reinforce purpose of Stand-Up

2.3.4.3.4. They will change when they need too

2.4. Sprint Planning

2.4.1. Why?

2.4.1.1. Know the work

2.4.1.1.1. understand

2.4.1.1.2. choose

2.4.1.1.3. task

2.4.1.1.4. volunteer

2.4.1.2. Get Fresh Start

2.4.1.2.1. renew sense of commitment

2.4.1.3. Commit on Shared Goals

2.4.1.4. Create Focus and Abundance

2.4.1.4.1. Team worry only about what they have committed for

2.4.2. preparation

2.4.2.1. Get Structure

2.4.2.2. having product backlog READY

2.4.2.2.1. DEEP: Detailed , Estimated, Emergent, Prioritized

2.4.3. How?

2.4.3.1. introduce the structure

2.4.3.2. hold time box

2.4.3.3. set back

2.4.3.4. listen for teachable moments

2.4.3.5. check in for progress

2.4.4. Teachable moments

2.4.4.1. Challenge the team on the REAL business value

2.4.4.2. Promote strong product Ownership

2.4.4.3. Uphold healthy role boundaries

2.4.4.4. Improve Tasking

2.4.4.4.1. Mind Mapping

2.4.4.4.2. Silent Tasking

2.5. Sprint Review

2.5.1. why?

2.5.1.1. True-up

2.5.1.2. Get direct feedback

2.5.1.3. Offer insight

2.5.1.4. Ask for help

2.5.2. How?

2.5.2.1. Speak in value first order

2.5.2.2. coach is insignificant

2.5.2.2.1. watch what is happening for and to the team

2.5.2.2.2. prepare some question to search for answer through the review

2.5.2.2.3. take note with exact words used

2.5.3. dealing with observation

2.5.3.1. Share with team

2.5.3.1.1. Team may strike about the observation

2.5.3.1.2. team may hear and not respond

2.5.3.1.3. team may not have the power to discuss on spot after review , do not push them

2.5.3.2. observation types

2.5.3.2.1. reinforcing

2.5.3.2.2. deepening

2.5.3.3. use observations and material for further discussions

2.6. Retrospective

2.6.1. why?

2.6.1.1. Inspect and Adapt

2.6.1.2. look back at how not what ?

2.6.1.3. Do even better next time

2.6.2. prepration

2.6.2.1. take notice through the sprint

2.6.2.1.1. it is not mandatory to reveal notes on spot knowing that retrospective is the best time to reveal them

2.6.2.1.2. coach should deal on spot if three were devastating problems

2.6.2.1.3. coach should honor not worrying the team about how are they sprinting

2.6.2.1.4. coach should have some area to look at while team sprinting

2.6.2.1.5. this is one of the continuous tasks that coach should be doing all the time

2.6.2.2. check with team members and product owners

2.6.2.3. prepare one or two point as the main theme of retrospective

2.6.2.4. prepare agenda

2.6.2.4.1. need to check the book Making good teams great to get some activities for retrospective

2.6.2.4.2. many interactive games could be used here , need to check the site training-youth.net , tools section for ideas

2.6.2.4.3. agenda could have two main topics

2.6.3. How?

2.6.3.1. make clear belief: Team know the rights things to do .

2.6.3.2. ask permission for the agenda

2.6.3.3. keep the time box

2.6.3.4. work towards a constructive outcome

2.6.3.5. invite them to write agreement

2.6.4. after retrospective

2.6.4.1. pay attention to the implementation of current agreement

2.6.4.2. look for situation that allow to hold agreement up to them

2.6.4.3. step back to agreement if the purpose of retrospective get twisted

2.7. quality of conversation

2.7.1. what is?

2.7.1.1. pay attention for the quality of conversation

2.7.1.1.1. this is one of the first skills that should be introduced to team so they can go ahead in the different conversation and of they did not go i can refer to our agreement on the quality of conversation

2.7.1.2. quality conversation is :

2.7.1.2.1. making sure everyone gets speak

2.7.1.2.2. truly listening

2.7.1.2.3. viewing each new idea as a gift

2.7.1.2.4. moving forward

2.7.2. How?

2.7.2.1. powerful observation

2.7.2.1.1. keep your observation for yourself for few minutes

2.7.2.1.2. consider your words carefully

2.7.2.2. powerful questions

2.7.2.2.1. open end question with no correct answers

2.7.2.3. powerful challenges

2.7.2.3.1. that is really amazing approach . I wish the nature of the business allows such creative practices and give "room " for that. I think such tools is really useful for hackthons / entrepreneurers . I really wish we are able to do that in the companies

2.7.2.3.2. I think challenging teams with bold ideas may need to have in mind some success stories to proof to them that bold ideas is not possible . It would be great if we managed to get these ideas form the same company we are in.

2.7.2.3.3. Amplify their thoughts or take it to wild directions

2.7.2.3.4. Be big

2.7.2.3.5. Be bold

2.7.2.3.6. get them dreaming a little bit

2.8. hint about facilitation

2.8.1. when team is new set with them physically, when team is developed and challenges is less set back

2.8.2. let them know and feel you can help them

2.8.3. let them notice that you contribute to diffrent levels

2.8.4. expect your mind in conversation especially if you are only watching

2.8.4.1. bring attention back Over and over again

2.8.4.2. keep your mind busy in background activities

2.8.5. when gets tense , back t team again

2.8.6. offer new skills in the teachable moments

2.8.7. Professional facilitation and Agile coaching are similar , there is a lot of resources on agile facilitation

3. Selected Statements

3.1. person is more important than formula

3.2. who made commitment will deliver it

3.3. always have a agenda , always adjust it on fly when needed

3.4. your job : to help each team member to take his next step in agile journey

3.5. your job: to help product owners to identify and really give priority for items of top business value

3.6. Teaching roles of agile coach and product owner are very important to avoid lot of conflicts

3.7. as coach in dealing with product owner (and i believe with all roles ): teach her , coach her , expect her playing the role, let the role fail (if not played ), help him learn from fail , recover together, become stronger

3.8. Facilitation : this is their meeting not mine

3.9. Having 30 things done yields more value than having 50 things in progress

3.9.1. this is one of my core values in life

3.10. /Product owners says "What" ,Team says "How? " and "How much? "

4. As Teacher

4.1. Start-up

4.1.1. how

4.1.1.1. Process

4.1.1.1.1. My Agile is not your agile problem

4.1.1.1.2. 10 min white board talk

4.1.1.2. lean about team

4.1.1.2.1. learn about each other

4.1.1.2.2. create shared vision

4.1.1.2.3. Creating team Norms

4.1.1.3. Teach about the work ahead

4.1.1.3.1. Envision

4.1.1.3.2. review product backlog

4.1.1.3.3. Get going

4.1.2. startup preparation

4.1.2.1. Good enough

4.1.2.2. insightful

4.1.2.3. Targeted

4.1.3. restart

4.2. Teaching new team members

4.2.1. getting in steps

4.2.2. let team tell about products and themsleves

4.2.3. Just talk and get him in

4.3. use teachable moments

4.3.1. old quote: Note all you know you say. not all you say , got its right time. Not all what get its right time got its audience.

4.4. Teach different Roles

4.4.1. Product Owner

4.4.1.1. Product Owner Roles

4.4.1.2. CRAK

4.4.2. Agile Manager

4.4.2.1. Roles

4.4.3. Agile coach

4.4.3.1. Roles

4.5. Glue things together

4.5.1. Teach roles interlocking

4.5.2. Teach that roles are not titles

4.5.3. Teach that roles help one another

5. As Problem Solver

6. As Problem Solver

6.1. It is team commitment not yours

6.2. Involve us in decisions that impacts us

6.3. Agile Problem solving

6.3.1. If problem violating a rule of agile , put your foot . Otherwise, It is your opinion

6.4. Problems Everywhere

6.4.1. Process Problems

6.4.1.1. I need to find some resources about health check for agile development

6.4.2. Quality Problems

6.4.3. Team Problems