GP Studios - Beta project team sprint
| This work belongs courses | https://edu.cnblogs.com/campus/xnsy/GeographicInformationScience/ |
|---|---|
| Where the job requires | https://www.cnblogs.com/harry240/p/11524196.html |
| Team Name | GP Studio |
| The target job | The project team sprint, BUG improve existing software functions and repair system |
| Team blog link | https://home.cnblogs.com/u/gy722/ |
1. Schedule
Sprint for 3 weeks and submit the Beta version release notes on the project deadline.
Note: Beta sprint for 3 weeks, submit a report on the completion of blog sprint during the week and, finally submitted one week Beta version of the release notes.
the first week
the next day
The third week
Estimated remaining tasks, assign tasks (development, testing, etc.). Submitted the first week sprint record content as required.
Estimated remaining tasks, assign tasks (development, testing, etc.). Submit a second week sprint record content as required.
Sprint reports were submitted to Beta release notes and the third week of the project.
2. sprint tasks required
to submit a weekly summary blog sprint (needs to be submitted one week last Beta version of the release notes)
to complete the test results after the Alpha release, project assessment and also what needs to be completed, and the completion of the work required time to determine the total amount of the expected remaining tasks. (Assignments in hours / man units).
Conduct daily meetings, each member to report their own work done today, PM division of tasks scheduled for tomorrow.
PM plotted according to the project burndown regular meeting each day.
PM do daily summary.
Note: Beta sprint aim of improving the Alpha version, more task should be to improve the function of the system as much as possible to solve the bug can be found in the weekly sprint blog to reflect and improve outcomes sprint, there is a marked improvement.
3. sprint blog content requirements
, please work next week to address the submission. (Week there will be a corresponding release sprint submit jobs, ask someone to pay attention!)
Reference Fuzhou University of the team work, to express my gratitude!
(1) SCRUM portion
Each member Description: My yesterday's achievements (which completed the task, how much time, how much time remains), the difficulties encountered, progress today resolved (see Requirements earlier plan), the plan tomorrow. (Can be listed in tabular form)
team members work must have if it is to develop the code check-in, check-given record corresponding Issue content and links, the code must be performed every day (the day of screenshots)
team members if it is a test and other work, and that there must be concrete results (screenshots, test reports, etc.)
photo of a SCRUM meetings, conferences photograph should be a real sprint day meeting of the non-swing pictures, can protect his face to protect privacy. (It can also be online meetings, requests for conference content screenshot.)
(2) PM Report:
The entire project is expected to amount of tasks (task = expected amount of time all the work) and time ( 'time is spent' all records) is now spent, but also the rest of the time ( 'time remaining' all the work)
PM Draw burndown (third-party tools can be recommended: use highcharts draw beautiful burndown, or their use Excel to do).
FIG burn requirements (Example: Example burndown):
of (h / person) as a unit, to everyone who needs long time together to get the total time of the remaining tasks.
The remaining task given the expected time to complete the task and the actual time remaining task time three fold lines.
If you find a new job in the course of the day you need to find time to increase the remaining tasks.
It does not have to be a smooth decline in the drawing but must be in accordance with the real situation of daily meetings.
Proper project procedures / modules of the latest (run) shots.
4.Beta release notes required
to give a list of team members.
Which problems were created in Alpha testing phase, and the tasks are not yet in the Alpha version.
Beta release of version given address or install Configuration Manual (available for download and operations, in order to reply when the project can be tested using the spot).
b / s structure of the program needs to deploy its own team server, the program will be published to the server, just given access to the IP address or domain name. No installation instructions; (eg: Site class)
C / S structure needs to be given Download client program, one can download and install the trial itself, the installation instructions need to be given. (Eg: stand-alone program, mobile APP, and others need to install client projects)
in both cases shall be given a simple user manual
Given instructions for use.
Summary gives the status of projects.
Members done.
What kind of problems encountered in the sprint Beta stage, how to solve.