1. Setting the context Setting the context at the beginning of any meeting is the first step you can take to ensure that the meeting is effective. Participants need to understand what the focus of the meeting is. You can start the meeting either with a pre-defined context, or you can define it real-time with the participants (“So, what is the context for this retrospective?”). Below are some sample contexts:
- “This retrospective is a bi-weekly recurring Scrum retrospective for the ABC team. We are on Sprint 12 out of 30.”
- “In 14 days, our artifact should reach the main production stage.”
- “Feature XYZ exploded in production, bringing the servers down for 2 hours until sys-admin could bring the older version back up.”
- “This team will work together in a new project starting today.”
- “We have worked together in the past year. We will be working together for another year to come.”
2. Prime Directive In Project Retrospectives, Kerth introduced the “Prime Directive”; a statement intended to help set the stage for the retrospective. The Prime Directive states: ‘Regardless of what we discover, we understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.’ The statement is invaluable to set the tone for the meeting.
本文分享自微信公众号 - 思特沃克（ThoughtWorks），作者：Paulo TC
原文出处及转载信息见文内详细说明，如有侵权，请联系 firstname.lastname@example.org 删除。
本文是对kubernetes GC proposal的解读分析，是对GC in kubernetes v1.3的内部结构剖析，并记录了其中一些关键点，以便日后能...
A. New Year Table time limit per test2 seconds memory limit per test256 megaby...