Gamma phase post-hoc analysis

Gamma phase post-hoc analysis

Vision and goals

1. Our software to solve the problem? Whether clearly defined? Is there a clear description of the typical user and a typical scenario?

• The problem we have to solve : Laboratory enrollment information is scattered and difficult to work with creativity and to achieve separation
• Typical users : at this stage for students and laboratory
• A typical scenario :

2 We reached the goal yet (function originally planned to do a few? Delivered as originally planned to deliver it? Originally planned to reach the number of users reached it?)

• Features original plan : cooperation, trust, creativity and publish basic functions of the Forum; cut off after a demonstration late to join the commission letter concerns collections and other functions within the lab station
• Delivery time : although the first phase of development there is a failure to postpone delivery, but Gamma completely finished as planned
• Number of users : 130+ preliminary achieve the desired goals

3. and on a stage compared to the quality of the software engineering team to improve it? In what has been improved, increase the number of specific, how to measure?

There is a certain improvement mainly reflected in:

• Teamwork : After a period of running, everybody's cooperation is gradually improving, everyone is aware of their responsibilities, to actively complete the task
• Quality of work : With the first two stages of the learning exercise, most of the time can be assigned to the development and reduce the time to learn new content, improve code quality, reduce the number of bug (single-stage reduction of five or six to a dozen bug)

4. The amount of users, user beforehand what's expected agreement on acceptance of the important functions and we? Our goal from the closer it?

Of users within expectations, but the user acceptance of the important functions and we expected some deviation. Users prefer to use more labs, which we adjusted the goals and consistent user.

5. What are the lessons? If history all over again, what would we do to improve?

• Lessons learned : Be sure to formulate a comprehensive plan, and implement a detailed argument. Some ideas before the discovery in the implementation process is not feasible to implement, adjust it frequently.
• If they can be repeated : the implementation of twinning the development of multi-party cooperation can be achieved of the argument, in-depth discussion of the details to achieve

plan

1. Is there enough time to do the plan?

Yes. You can come up with a half weeks in advance planning and discussion.

2. Team at the planning stage is how to resolve the disagreement colleagues for planned?

The actual disagreement did not have a lot, we pay attention to consider the views of developers.

3. You work planned if finally done? If you have not done, and why?

We have been completed. Cut off the unwanted part, also added some new ones.

4. find that you do not have some hindsight did not need or do not count for much?

not at all. Some features (commission) before doing have found do not need, then cut off in advance.

5. Is each task are clearly defined and measurable deliverables?

Without being too specific delivery standards, consider the practical implementation of double standards, requirements specific to the content of the page, but not rigidly stick format.

6. The whole process if the project were carried out according to plan, the project what had happened? What risk was not estimated, why not estimated?

The presence of alpha stages of development failure, beta phase found some extra features, and to re-learn new knowledge. Project personnel move too important, all the back-end technical personnel transfer, resulting in the backend rewritten. I did not expect it will be very tight time struggling to cope with risk.

7. There is no buffer left in the plan, the buffer role it?

There are two or three days to leave the buffer. Buffers are used to fix some bug feedback function and an increase in small whim.

8. Future plans will do what changes?

Incorporated into everyone's personal affairs planning, a more rational allocation of tasks.

9. What have we learned? If history all over again, what would we do to improve?

Polymerization same task delivered a complete person, not rigidly stick to balance assignments, improve quality of the coupling.

If you do it all again, we will be dynamic mission planning, reduce busy wait phenomenon.

Resources

1. We have enough resources to fulfill the tasks it?

Lack of time resources. Sufficient machine resources.

2. The time and other resources required for each task is how to estimate how accuracy?

Code amount and the code according to the quality assessment, the final stage of good accuracy.

3. Test of time, manpower and software / hardware resources are sufficient? For those without programming resources (graphic design / copy) whether underestimate the difficulty?

Testing time a little nervous, but also a little nervous manpower (5). Adequate hardware resources, not much does not require programming resources, the difficulty is not great.

4. Have you ever felt that you can do to let others do the (more efficient)?

There are indeed part of the task can be delivered the same people to do more efficient and quality.

5. What are the lessons? If history all over again , what do we do to improve ?

Human and time resources will greatly affect the progress.

Ruoguo over again, we will recruit more than two members at the start of the Beta stage.

Change Management

1. Each relevant employees in a timely manner that the message changed?

Yes. We will communicate and push workers took over the group after the completion of realization.

2. What measures we have adopted a decision "to postpone" and "must be achieved" feature?

According to user traffic and user feedback, a weight adjustment.

3. The conditions of export project (Exit Criteria - what "done") have a clear definition of it?

We have three criteria: beautiful, practical, no bug.

4. For possible change whether contingency plans?

Yes, it will concentrate on solving problems.

5. Are employees able to effectively deal with unexpected work request?

Yes, team members can handle the additional task requests in a timely manner, and to achieve self-development to achieve the following functions.

6. What have we learned? If history all over again , what do we do to improve ?

Everyone should do their own thing, in charge of the team.

If it can again, we will require the use of a small amount of time to write some comments, and Cadogan development of the document, but the fact of our time is not sufficient.

Design / implementation

1. Design work at what time and by whom done? Is the right time, the right man?

Designed jointly by all members in achieving begin at the beginning, is the right time with people.

2. Design work has not encountered ambiguous situations, how the team is resolved?

Part of the content can not be determined, it was left to try to choose the development, focused on developers to consider the views.

3. Does the team use unit testing (unit test), test-driven development (TDD), UML, or other tools to help design and implement? These tools work? UML Documentation beginning of the project and compare the current state What is the difference? How do these differences arise? Do you want to update UML documents?

The use of the test unit designed to help achieve a certain effect. Relative to the start of the project UML basic push to rewrite, because we rewrote the backend.

4. What is the most versatile Bug produced, and why? After publishing discovered something important bug? Why did not we think of these cases in the design / development time?

Bug up the communication station, the channel repeatedly transmitted phenomenon occurs station, deletion phenomenon. The main test is not very comprehensive, and the test time is not enough, before the release of the full realization of functions difficult to test.

5. Code review (Code Review) is how to proceed, whether the strict implementation of the code specifications?

Code review mainly by the development manager of the front and rear end, specification is not very strict, we need to improve.

6. What have we learned? If history all over again, what would we do to improve?

Agile project must be good to deal with all kinds of unexpected situations, planning ahead of time to complete.

If we can again, we will prepare one to two days ahead of schedule throughout, leaving enough buffers stability testing.

Test / release

1. Does the team have a test plan? Why not?

Team had a rough test plans, test personnel have a detailed test plan.

2. whether formal acceptance testing?

An official acceptance, failure to fight back changes.

3. Does the team have the test tools to help test?

Used Django coverageto track our unit test code coverage, improve and improve.

4. The team is how to measure and track the effectiveness of the software? From the results of the actual operation of the software, these tests work useful? What improvements should have?

Mainly stress tests. From the testing point of view, to find some extra code, but not very useful to enhance the limited, major improvements will depend on the implementation code.

5. discovered what unexpected problems during the release of?

Password change can be changed to any format, we neglect test.

6. What have we learned? If you do it all again, what would we do to improve?

Our experience : the need for a sufficient number of tests to ensure stability.

If all again : to demonstrate the improved implementation of the code, to achieve additional acceleration.

The role of team management, cooperation

1. how each team is to determine the role, is not the best use?

Consider a personal opinion, we all do want to work.

2. There it among team members help each other?

Some, pair programming habits continued the entire development process.

3. When the emergence of project management, when issues of cooperation, team members how to solve the problem?

Identify those responsible, discuss and revise again, face to face to discuss the way is very effective.

to sum up

1. Do you think the current state of the team belongs grade CMM / CMMI in?

We believe that, after the overall development process, our team has basically reached the "management level" requirements.

2. Do you think the team is currently in the bud / running / specification / create what stage of a stage?

We feel that our team reached a "standard" basic requirements phase, has been relatively high consciousness and sense of responsibility, cooperation does not appear contradictory, feeling good about each other.

3. What do you think most need to improve aspects is?

Code specifications. This problem has been repeatedly stressed, but still occurs frequently, different members felt that standards there are some differences.

4. Comparison agile principles, what do you think your team is the best?

Deal with a number of unexpected events, difficult to reach the end.

• There is a failure to develop versions
• Back-end developer transfer
• Panel members time constraints (work, laboratory, competitions, examinations)

However, we finally completed as planned development.

5. In the next stage we want improvement

• Stability: increasing the pressure load capacity, optimize the code architecture
• Code standards: strict format requirements, increased scrutiny
• Strengthen the publicity work: the number of users is not much we need to be more broad-based publicity

Team members pictured

(Mm classmates back home one week, there is no photo below the line)