Chris lucian
Wednesday, February 3, 2016
Checklist manifesto
Checklist manifesto.
[ ] Team must come up with it.
[ ] Not too many items.
[ ] Critical for the task at hand
[ ] When? Before deployment. Db schema change. When website goes down.
[ ] Quick to perform, unique to the situation and repeatable.
[ ] Not a huge matrix.
[ ] Task oriented.
[ ] Way to self organize.
[ ] Automate it if possible.
[ ] On boarding a new employee
[ ] Checklist for definition of done.
[ ] Documentation, move user story card. Unit tests, etc.
[ ] Things to be delegated.
[ ] Share your checklists.
[ ] Update a single copy. Source control?
[ ] The expert is not the right person to make the list, but should be involved.
[ ] What to do, not how. (Link the how)
[ ] Why are we doing these items?
[ ] Checklist is not a test.
[ ] Use them! GTD. Get things done. Make it a habit to use checklists.
[ ] Prune your checklists. Less is better.
[ ] For times when you must think fast.
[ ] Find the pause points. Before deploy. When something goes wrong. When a new person joins the team.
[ ] Discover what is essential.
[ ] TDD is a checklist. What is the next condition you would like to test for?
[ ] Checklist for building checklists. See book. Checklist manifesto.
[ ] Could be pictograms.
[ ] Checklist smells. Too long. Not performed. Tooany paths.
[ ] Remove ego barriers.
[ ] Teachable moment when something goes wrong.
[ ] Model how things go right with checklists.
Agile Homesteading: What To Do When You Have To Grow Your Own Product Owners
Margeaux Bucher
February 3, 2016 1:00 PM
We discussed the minimum viable product for product owner duties and skills. Then graphically laid them out from the most basic and most wanted through to the most advanced. This groundwork set up a frame work for what to focus on first when training a brand new product mom owner, both to avoid their overwhelm, and met the teams basic needs as soon as possible. We also filled in the Chart with specific tips and tricks to growing product owners in many of the brainstormed skills.
Facilitating Agile Teams
While sometimes called a manager or leader, I propose that the more correct title is facilitator. Let's have a discussion about that role and what is needed to be successful which should finds its definition in what is like to have a successful team.
Traits of a good facilitator.
- Removes impediments
- Promotes harmony
- Promotes communication
- Promotes a safe environment
- Appropriately handles urgent or perhaps not urgent issues
- Adequately shields team
- Encourages learning
- Empowers the team
Techniques used by a good facilitator
- Is an example
- Procuring agile team members
- Shares ideas
- Has retrospectives
- Shuts up when needed
- Creates development plans, requests 360 feedback
- Asks questions that coach
- Creates a social environment ( team events)
- Maybe uses per pressure
- Concensus on decisions
- Disagree but commit
- Experiments with time box or metrics
- Push limits
- Use lean coffee
Subscribe to:
Posts (Atom)