Stand-up meeting

stand-up meeting (or simply "stand-up") is a daily team-meeting held to provide a status update to the team members. The "semi-real-time" status allows participants to know about potential challenges as well as to coordinate efforts to resolve difficult and/or time-consuming issues. It has particular value inAgile software development processes,[1][2] such as Scrum, but can be utilized in any development methodology. The term "stand-up" derives from the practise of having the attendees stand at the meeting, as the discomfort of standing for long periods helps to keep the meetings short.

The meetings are usually timeboxed to 5–15 minutes and are held standing up to remind people to keep the meeting short and to-the-point.[3] The stand-up meeting is sometimes also referred to as the "stand-up", "morning rollcall" or "daily scrum".

There are three questions to ask and answer in the daily stand-up.[4] Though it may not be practical to limit all discussion to these three questions, the goal is to stick as closely as possible to these questions:

  1. What did I accomplish yesterday?
  2. What will I do today?
  3. What obstacles are impeding my progress?

The meeting usually takes place at the same time and place every working day. All team members are encouraged to attend, but the meetings are not postponed if some of the team members are not present. One of the crucial features is that the meeting is intended as a communication vehicle for team members and not a status update to the management or other stakeholders. Although it is sometimes referred to as a type of status meeting, the structure of the meeting is meant to promote follow-up conversation, as well as to identify issues before they become too problematic. The practice also promotes closer working relationships in its frequency, need for follow-up conversations and short structure, which in turn result in a higher rate of knowledge transfer – a much more active intention than the typical status meeting. Team members take turns speaking, sometimes passing along a token to indicate the current person allowed to speak. Each member talks about progress since the last stand-up, the anticipated work until the next stand-up and any impediments, taking the opportunity to ask for help.[5]

Team members may sometimes ask for short clarifications and make brief statements, such as "Let‘s talk about this more after the meeting", but the stand-up does not usually consist of full-fledged discussions.[citation needed]

References[edit]

  1. Jump up^ "Agile Testing". Borland.com. Retrieved 2010-01-27.[dead link]
  2. Jump up^ "Agile Stand-up on Agile Testing". Borland.com. Retrieved 2010-01-27.[dead link]
  3. Jump up^ "It‘s Not Just Standing Up". Martin Fowler.
  4. Jump up^ "Scrum Guide". scrum.org.
  5. Jump up^ "Daily Scrum Meetings". Mountain Goat Software.

External links[edit]

Categories:

Stand-up meeting

时间: 2024-11-03 02:57:36

Stand-up meeting的相关文章

stand up meeting 12-2

今天因为各位组员组里项目原因没有集中在一起进行stand up meeting.但是士杰和天赋国庆分别对项目进度和前后端的结合进行的沟通. 针对后端部分,天赋完成了GetRankingData API的获取和本地缓存的存储,并且通过了单元测试.之后士杰完成了GetScore和Time的函数原型.因为前端的答题界面还需两天左右时间完成,所以我们模拟了GetRankingData的Input对后端逻辑进行测试.接下来天赋和士杰会帮助国庆完成前后端的连接,这样答题界面完成后,我们就将项目推进到答题结果

stand up meeting 12-8

根据计划今天项目组成员和travis老师毕然同学进行了最后一次关于design和feature的确认meeting. 项目design和UI的改动较大,feature改动较小,需对UI进行重新整合,对后端代码进行小幅度的refactor,详细信息如下: 1.单词挑战入口:根据travis所讲的数据分析,单词挑战模块的活跃度并不高,将单词挑战的入口放到单词本界面.如下图: 这会对项目的造成如下的改动:我们需要将单词本的name和QPName进行mapping,以支持后续的get rank data

stand up meeting 12-10

今天项目会议正好利用了大家上课前的十五分钟,大家对项目进度和项目中所遇到的问题进行了沟通. 由于天赋同学与重阳小组沟通及时有效,在mapping的过程中直接将单词本中的type与我们单词挑战中的question pool绑定,减少了我们很多后端代码refactor的工作. 答题页面中的点击跳转和check in提交部分的refactor也已经完成. 错题list的展示部分也已经完成,这一部分工作主要也是集中在前端展示的重构上. 静文同学在前端的滑动切换题目上遇到一点问题,主要原因是对前端控件的不

stand up meeting 12-9

今天项目小组本已约好在今天下午四点半进行今天的daily scrum: 但是在四点半的时候,天赋和士杰同学均因组内项目会议延时,导致今天的daily scrum只能在晚上进行,但静雯同学因身体不舒服无法参加晚上的meeting. 我们也将在明天人员齐整的meeting时记录下scrum照片. 天赋同学完成了与重阳组同学的沟通与协商,并完成了name mapping的工作. 因为这个feature是周二才确定,与travis商量后我们这次采用hard code的方式解决此问题,在第二个releas

stand up meeting 12/11/2015

part 组员 今日工作 工作耗时/h 明日计划 工作耗时/h UI 冯晓云 完成单词释义热度排序:允许用户自主添加释义:完成了button位置的修正(finally)和弹窗的美化:     6 try the backup plan    6 PDF Reader 朱玉影       logic1: 周以舟  --------------   --  -----------  -- logic2: 林建平         pdf 阅读器 张葳          注:周以舟同学未返回 UI——2

stand up meeting 11/16/2015

第一周,熟悉任务中~ 大致写下一天的工作: 冯晓云:熟悉bing接口,本意是调在线的必应词典API,参阅了大量C#调用API开发.net的工作,[约莫是因为有个窗口互动性更强,所以这样的工作更有趣,也更容易找到]然而我的任务只是要生成一个DLL供其他部分调用,所以然并卵~bug粗线在读取URL时,System.Net.WebRequest下找不到GetResponse(),或者是直接找不到WebClient,一度以为自己机子有问题,失控~由于是第一次接触C#,各种百度也没能解决,后来发现同样的代

stand up meeting 12/29/2015

part 组员                今日工作              工作耗时/h 明日计划 工作耗时/h    UI 冯晓云 重写popup UI添加笔记功能     6 mergeUI与reader   6 foxit PDF Reader 朱玉影       login 周以舟         sync 林建平         foxit PDF Reader 张葳         注:朱玉影,张葳今天晚上返校,归期较晚 popup UI 3.0: 本来今天应该完成reader

stand up meeting 12/10/2015

part 组员 今日工作 工作耗时/h 明日计划 工作耗时/h UI 冯晓云 修改了详细释义的自动换行功能:设计并完成了背景图片的切换功能    6 完成单词释义热度排序    6 PDF Reader 朱玉影 今天一天都在忙其他事情,没有来的及做  0  希望能够读取,解析pdf  6 logic1: 周以舟  --------------   --  -----------  -- logic2: 林建平         pdf 阅读器 张葳          注:周以舟同学未返回 UI——

stand up meeting 12/7/2015

part 组员 今日工作 工作耗时/h 明日计划 工作耗时/h UI 冯晓云           PDF Reader 朱玉影     学习pdf分析,渲染等api并且试着编写pdf reader        6 计划根据api文档和一些示例编写完整的分析渲染工程   6 logic1: 周以舟         logic2: 林建平         pdf 阅读器 张葳         

stand up meeting 11/24/2015

组员 今日工作 工作耗时/h 明日计划 计划耗时/h 冯晓云 规范在线查词的各项请求,将返回结果解析成树状,并定义完成各种操作以方便其他部分完成调用,排序,增删等操作 3 将它与朱玉影负责的数据库对接 3 朱玉影  基本数据库编程工作 4  释义部分在数据库中的存储  4 张葳       林建平         周以舟         说明:虽然必应词典的返回结果本身就是树状,但是我们所需的只是音标和简单的释义,为了方便各部分之间的通信,做成了string,所以在数据库部分时要恢复成树状存储: