软件工程 - 团队重组

In software companies, as in many corporations, the only thing that is not changed is “change” itself. A change in team membership and structure is usually called “re-organization”, or “re-org”. In sports, we call it “转会季节”.

At the beginning of this class, 5 teams were formed after a short period of chaos and excitement. Many students joined various teams based on incomplete info, a hutch, or just the need to have a team. Now after the alpha stage, I bet everyone has a clear and deep understanding of what does it mean to ship a software – your team’s software. There could be several reactions:

a) This project is great, I’ll keep working on it in Beta stage, and after that!

b) This project is ok, I’ve done my part. I want to try a different project to practice my other skills, can I?

c) I have different opinions about this project, and we can’t convince each other, so can we go different ways, and still be friends?

d) I don’t care what kind of team I’m in…

e) We love this project, but we need more hands to help out!

f) …

So it seems we need an re-org after Alpha. In my past ASE class with USTC students, I had tried the “re-org” and some people didn’t like it – mostly because they don’t like surprises. To reduce the amount of surprises, I’m telling you this news ahead of time, so that you can prepare for it.

1) When will this re-org happen? Right after Alpha release

2) What is going to happen exactly?   Each team will decide one or two team members leaving the team.   Each team must take at least one new member from other teams.

3) What’s the process to decide?    The PM/leader of the team will decide which process the team will take (e.g. dictatorship, consulting, vote, consensus, random number, etc), and the PM will report to TA and me their names.

4) Where will these “free members” go? they can pick their next team (got to be a different team), they can negotiate with other teams. Of course, if your team needs more people, it’s a good time to recruit talented classmates.

5) What if no team wants a “free member”?   if all negotiations fail to work, by default, the free members will go to the next team in order (e.g. from team1, go to team 2; 2 to 3, … 5 to 1).   The receiving teams have to accept these members.

6) Of course, the departing team members need to have good documentation of his/her work (remember to write comments in your code!), and the new member needs to learn quickly how to work on a “legacy system”, this is part of skills in Software Engineering,

Some people might feel this is a bit chaotic, but great people can thrive on chaos, so enjoy the re-org!

软件工程 - 团队重组相关推荐

北航 2012 秋季现代软件工程团队项目要求
同学们的小组要在下次课上 (10/15) 决定做哪一个项目 (按次序挑选), 确定之后写团队博客描述他们要做的究竟是什么系统 (不懂的地方可以在博客上提问). 这次课程有10 个学生团队, 我们有 ...
17秋软件工程团队第五次作业 Alpha
题目:团队作业--Alpha冲刺 17秋软件工程团队第五次作业 Alpha 12次Scrum 第一次Scrum 第二次Scrum 第三次Scrum 第四次Scrum 第五次Scrum 第六次Scr ...
17秋软件工程团队第五次作业 Alpha Scrum3
17秋软件工程团队第五次作业 Alpha Scrum3 今日完成的任务杰麟:java后端学习: 世强:Android的部门基础信息模块的信息显示和对接后台: 港晨:后台管理登陆界面ui设计: 树 ...
软件工程—团队作业1
软件工程-团队作业1 团队称号:Thanos (灭霸,超叼的一个动漫人物) 团队成员: 队长成凯 1600802002 博客链接: http://www.cnblogs.com/ck03/ 党 ...
17秋软件工程团队第五次作业 Alpha Scrum2
17秋软件工程团队第五次作业 Alpha Scrum2 今日完成的任务杰麟:Java后端的学习: 世强:登录和注册接口编写: 港晨:完成数据库表的设计: 树民.陈翔:完成超级管理员后端框架. 其 ...
面向对象方法及软件工程——团队答辩
健康助手小程序码(扫码可体验) 一.团队成员的姓名.学号及博客链接地址姓名:陈颜如玉学号:1700802118 博客链接地址:https://www.cnblogs.com/chenyanruyu ...
17秋软件工程团队第五次作业 Alpha Scrum9
17秋软件工程团队第五次作业 Alpha Scrum9 今日完成的任务世强:APP后端部门申请状态: 港晨:主页面代码实现: 树民:完善超级管理员web后端: 伟航:设置页面和侧边栏的原型: 陈 ...
17秋软件工程团队第三次作业预则立他山之石
题目:团队作业-预则立&&他山之石团队: 我说嘻(xì)哈(hà)你说侠 17秋软件工程团队第三次作业预则立&他山之石 1.确立团队选题,建立和初步熟悉团队git的协作 ...
17秋软件工程团队作业同学录
题目:团队作业--随堂小测(同学录) 17秋软件工程团队作业同学录 Github Classmate-book 提交日志截图在现场带了两台笔记本,用两个人的账号进行commit: PR: 程序 ...

软件工程 - 团队重组

软件工程 - 团队重组相关推荐

最新文章

热门文章