Modern Software Engineering Operations 3 team operations

Document directory

•  
• Team homework #2: innovation in new application domains.
•  

This is a list of assignments for modern software engineering courses. Instructors can select jobs based on their needs. We recommend that you ensure that assignments are available every week.

Team assignment Team Homework: Suitable for the assignments completed by the Team

All these assignments can be completed only when the team members cooperate with each other. The team can select a student to complete the specific writing and blog part of the assignment. You can take turns to complete the assignment. A team is usually composed of 5-7 members. Therefore, even if you have homework every week, it is only one of the team members who want to do text work. Therefore, the burden is not heavy.

Team Homework #0: Collect student feedback about SE courses

List Group members' profiles and photos.

Collect feedback from students who have previously attended common software engineering courses. It mainly includes the following content:

Class, grade.

Course Materials and lectures

Internship Program of the course

Average number of codes written by students

Student feedback on the course

Example:

Interview with senior student of Assignment 1 of modern software engineering

Assignment 2 of modern software engineering-similar courses of Information College

 

 

Team Homework #1: interview past projects

For each team, pick a past Software Engineer Course project (either done by USTC team, or by Tsinghua students), Interview students of that team, read their blogs, and report on your learning, then publish to your team blog.

§ Did they reach their goals in project? How many users do they have?

§ Lessons learned from them,

§ And what wocould you do differently if you were in that team, or if you cocould re-do the same project from scatch.

§ You can interview by face to face talk, email, phone, or interview their users.

Please post your homework to your homepage.

Deadline: 2nd week

Example:

"Cube Teaching and Research Section" autopsy report

Http://www.cnblogs.com/SE-team-2011/archive/2011/02/28/1966921.html

Team homework #2: innovation in new application domains.

Please read books about innovation, and blogs about innovation, e.g. I have several:

Http://www.cnblogs.com/xinz/archive/2011/07/09/2102052.html

Http://www.cnblogs.com/xinz/archive/2011/07/10/2102310.html

Http://www.cnblogs.com/xinz/archive/2011/07/11/2102667.html

I had an old assignment for PKU students:Http://www.cnblogs.com/xinz/archive/2011/06/26/2090631.html.

Now I 'd like to see you do the same thing with Weibo, or group buying.BlogAll are replacedWeibo, OrGroup Buying), Since we have 4 teams, I 'd like to see team 1 and 2 pick Weibo, team 3 and 4 pick group buying.

Deadline: 8th week

You need to apply accounts, and use these accounts for a period of time in order to have meaningful investigation. So I suggest you start early.

Example: team assignment-Weibo Website Survey

Team homework #3: how does your team evaluate member's performance?

Please have a team meeting and decide how your team plan to evaluate each member's performance.

See this blog for details.

Deadline: 3rd week

Team homework #4: your proposal for your team project

Following the NABC format

How to provide reliable project suggestions for modern software engineering teams

Deadline: 4th week

 

Team homework #5: spec of you most important feature

PM of each team need to write a blog, sharing the spec of your most important/challenging feature.

What's is your project NABC?

Who is your typical user?

What is the scenario?

 

Deadline: 10th week

  Team homework #6: Test Plan and Test Matrix

Write a blog to describe in detail how you're going to test your software based on scenario and persona

1. your test plan

2. the personas (typical character) of your software

3. How do you perform CT different personas (some teams have 3 personas) to use your software? What's their need and their goals, how your features work together to solve their needs?

4. Your test matrix (test matrix)

On what platform, what language, what type of machines, what type of browser, etc. to test your software?

5. What is "exit criteria" (good enough) for your software for beta release?

Hint: focus on the first 5-15 minutes.

Deadline: 11th week

Team homework #7: Alpha/Beta Stage Scrum report (repeat this for Beta Stage)

Report the progress of 10 day scrum, each daily report shoshould contain:

A) what was achieved by each person yesterday (list specific work item #)

B) what to do today (list specific work item #)

C) what is blocking each team member?

D) show the "burn down" chart of the team progress.

Post this report as a blog, for 10 consecutive days,

 

Team homework #8: Alpha Release

Write a blog post to show your Alpha release

 

Deadline: Alpha release week (recommended: 7th week)

Team homework #9: Alpha Release Postmortem

Write a blog to show what the team has learned in the alpha stage. You can use this template to help the discussion:

Modern software engineering handout 4 methodology-Zhuge Liang meeting afterwards

Deadline: 1 week after Alpha Release

Team homework #10: Bug Bash

Each team has released beta version Code Complete. students can test each others's release.

To do:

A. Team 1 will test team 2's product

B. Team 2 will test team 3's

C. Team 3... 4

D. Team 4 will test team 1's product

Each team shoshould make their product/site ready for testing before the 14th week

Score: the team logging most bugs will win.

Please read <migration path>, my blog, or other doc for the guidelines of open a good quality bug.

For bug bash, a bug must meet the following criteria: 1) A subject started with "Bug Bash :..." The subject shoshould summarize the problem. 2) In the body of the bug, report your "steps of reproducing the bug", a short form is "repro :" 3) then report what do you have CT. Start with "Your CT :" 4) Then report what happened, start with "result:" If your bug doesn' t meet such criteria, it will not be counted as a "bug bash" bug.

Due date: right after beta Code Complete (12-14th week ).

  Team homework #11: Zero Bug report

Please triage all the bugs, all team members look at each bug and decide one of the following:

Must fix (P1)

Important to fix (P2)

Nice to have (P3)

Won't fix (for partial reasons)

You will use the next several days to fix ALL bugs, and get to 0, then you can have a Zero Bug Build, your product in this build is called Release Candidate 1 (RC1 ), you then test it to make sure it's great, if not, you fix more bugs, and have a RC2, RC3, etc.

When you're sure you got a good enough product, you will turn the RC into a real release.

Write a simple blog to show your team has reached Zero Bug. please attach a screen shot of your team project's bug list (how many P1/2/3 bugs), how many bugs you don't plan to fix, and why.

 

Team homework #12: Beta Release

Write a blog to show the world that you have released beta product.

 

Deadline: 15th week

 

Team homework #13: Alpha Release Postmortem

Write a blog to show what the team has learned in the alpha stage. You can use this template to help the discussion:

Modern software engineering handout 4 methodology-Zhuge Liang meeting afterwards

 

Besides the standard template for Postmortem, each team shoshould also report the following:

1. How can I improve the practice and alpha phase of each member in the beta phase?

2. list specific improvements for each person.

3. What alpha lessons have the team learned during beta?

Among the 12 agile development principles, the best and worst teams can list two points.

Http://www.cnblogs.com/xinz/archive/2010/12/11/1902849.html

Http://www.cnblogs.com/xinz/archive/2010/12/10/1902725.html

Http://martinfowler.com/articles/newMethodology.html

5. Compare The Cathedral and the Bazaar (Cathedral and market) to The software team's model (link). Which of the following is your team's development model? What are The advantages/disadvantages?

Http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar

Http://www.catb.org /~ Esr/writings/cathedral-bazaar/ar01s13.html

Deadline: 1 week after Beta Release (16th week)

 

Team homework #14: Final review(16th week)

A. TA will book a room for students + reviwers.

B. each team need to have app, video recording, spec, etc. ready. (please post these to your blog as well)

C. each team talk to users of your product, and record their feedback (text, audio, video). summarize that as a blog.

C. each team shocould have real user's feedback to show how good your product is.