T-code: OVA2, OVA0
Reference: http://scn.sap.com/docs/DOC-44777
Reference: http://scn.sap.com/docs/DOC-44777
星期二, 九月 15, 2015
星期二, 八月 04, 2015
星期一, 七月 20, 2015
星期三, 七月 15, 2015
星期二, 六月 16, 2015
4L Retrospective
What is 4L retrospective?
by Mary Gorman and Ellen Gottesdiener
We liked it when a good thing took on a life of its own.
We learned that it really resonated with many folks.
We lacked sharing the full understanding of the technique.
We longed for more sharing.
We learned that it really resonated with many folks.
We lacked sharing the full understanding of the technique.
We longed for more sharing.
"Many moons ago we wanted some variety in eliciting feedback, collectively sharing that feedback and exploring action possibilities. We decided to create a variation of World Café whereby areas of the room are used to focus on a specific retrospective topic. "
Steps for the 4 L’s:
1. Hang four posters, one for each L, around the room, titled appropriately.
2. Ask team member to write down what they Liked, Learned, Lacked, and Longed For – one per sticky note.
3. When the time is up, silently place their notes on each post.
4. Group duplicate sticky notes together and then discuss one by one.
Remarks for first usage:
Should always consider using DT room first for retrospective meeting. ( Big / White board / Post-it)
Book long period of time(2h). It just takes time to warm up and thinking.
Consider learned as a learning pool. Think about what is valuable and could share.
Book long period of time(2h). It just takes time to warm up and thinking.
Consider learned as a learning pool. Think about what is valuable and could share.
Difference between lacked and longed:
Lacked aims just for short term while longed aims for long term.
Usually longed is not easy to solve in a short period of time or cannot be resolved on your level.
Consider longed as long time plan, collecting feedback and discuss regularly.
Sometimes action(start discussing) is more important than result.
Dig deep enough to find out root cause.
Sometimes action(start discussing) is more important than result.
Dig deep enough to find out root cause.
Missed / not used:
Divide to 4 group discussion and shared result later on.
How to encourage team to express idea freely? ( Beer maybe a good starting point )
How to followup longed in next retrospective meeting?
What's the benefit for 2 team running retrospective together? ( Or how to max this point, what is the difference?)
How to let team member to dig out root cause and how to follow up?