Leader blog link
Reference Zou Yan teacher's question template Concluding Thoughts
Vision and goals (2 points)
1, our software to solve the problem? Whether clearly defined? Is there a clear description of the typical user and a typical scenario?
- Solve the problem of
our software is designed to solve the difficult early Charms users such as cars, Car difficult problem, the user can choose to ride through Pickme platform, Express travel, you can also rent social idle vehicles. After the campus market operations mature, we will expand the urban market, providing Pickme travel programs for the community users. - Clearly define whether
through our early needs analysis, surveys, group decision-making within a range of software after the final definition of the audit, we believe that this is both a complete definition and robustness of a piece of software. In our view, very clearly defined, welcomed the junior partner in question put forward your valuable comments. - Typical users
- Not on campus for the purchase of electric cars, bicycles user.
- Towns and cities rely on public transport, motorcycle travel user.
- Typical scene
- Scene One: the peak of the school campus, students can not wait for white, can not find a shared bike, but there are many users of electric vehicles backseat idle.
- Scene Two: Wang wanted to go to the market town center, but the location is relatively remote, waiting for the bus for a long time, and no motorbike taxi driver after.
More through our platform for rapid taxi, convenient travel. (image)
2, we reached the goal yet (function originally planned to do a few? As originally planned delivery time delivered what? Originally planned to reach the number of users reached it?)?
- The achievement of planned features
- Partially achieved, ride, Express achieve short car was not completed.
- Front-end interface to achieve beautiful, easy to operate.
- Set up the back-end database server, deficiencies in response fast enough.
- Whether the planned delivery time delivery
- It is that we complete the corresponding work in the defense the day before yesterday.
- The number of users has reached the original plan expected
- The original plan is not expected to have users, but for testing within our team.
3, number of users, users in advance of the expected acceptance of what is consistent and important functions we? Our goal from the closer it?
- Users amount in line with expectations.
- When the final product out, we are still very happy with team members to achieve our function.
- We have infinitely close distance of our goals.
4. What are the lessons? If history all over again, what would we do to improve?
- Technical aspects
- Before and after the beginning of the end of the interface definition is not standardized, resulting in integration difficulties
- Initially not use uni-app front-end project development, front-end code is the html file, causing no way to use the uni package to other platforms, are made pages.
- Non-technical aspects
- Reasonable time schedule is not enough, we have completed nearly 50% of the workload before the start of the sprint alpha, but alpha sprint stage, most of the members have a variety of tests, the slow progress of the project are focused on defense Two days before completion.
- Task allocation is relatively reasonable, the capacity can be allocated according to the size of each person.
- Contribution proportional distribution is not scientific, subjective factors significantly.
Plan (5 points)
1, if there is enough time to do the plan?
- We have a good pre-assigned tasks on time is sufficient, but in the end be delayed due to various reasons, the general progress.
2, the team at the planning stage is how to resolve the disagreement colleagues for planned?
- Our group assignments is relatively reasonable, barely different opinions, some small differences can be resolved through negotiation.
3, the original plan if you work finally done? If you have not done, and why?
- Wang Yaoxin, Galaxy Lin, Chen Zhirong, Xupei Rong, Shen Zi Yao, Lin Ming Town, Teng Jia, He Jialin, Chenxiang Yi, Chen Chaoying.
4, you do not find some hindsight did not need or do not count for much?
- The front end of the beginning of the development of the direct use h5, did not follow the norms HBuilder, take a detour.
5, whether each task are clearly defined and measurable deliverables?
- Each task has a clearly defined, no scientific measure, accounting for more than subjective factors.
6, the whole process if the project were carried out according to plan, the project what had happened? What are the risks was not estimated, why not estimated?
- Not all according to plan, the project was a bottleneck, build servers, network requests, embedded maps, we have no relevant experience, it slowed down the progress of the project.
7, there is no buffer left in the plan, the buffer role it?
- No, because at that time estimated for each task sufficient time.
8, future plans will do what changes? (Eg: buffer defined, overtime)
- Scheduled centralized knock code.
9, What have we learned? If history all over again, what would we do to improve?
- Learn h5, vue, flask, js, SQL server, network requests, if history again, we will re-allocate each person should have a good job, good project supervision, to ensure timely completion on schedule.
Resources (3 points)
1, we have enough resources to fulfill the tasks it?
- No, our team members have no experience of project development is done in learning by doing in.
2, time and other resources required for each task is how to estimate how accuracy?
- Time and other resources required for each task are based on historical experience and advice predecessors, the general accuracy.
3, the test of time, manpower and software / hardware resources are sufficient? For those without programming resources (graphic design / copy) whether underestimate the difficulty?
- Sufficient manpower, lack of software / hardware resources, test methods rough, basically rely on pure hand. I do not underestimate that do not require programming resources (graphic design / copy), allocated more experienced person to complete.
4. Have you ever felt that you can do to let others do the (more efficient)?
- No, everyone can play to their strengths, to do their own terms to achieve the ultimate (or at least the highest levels of our group), so that everyone is irreplaceable.
5. What are the lessons? If history all over again, what would we do to improve?
- Front-end heavy task, less than forecast, it should deploy more staff.
Change Management (4 points)
1, each of the relevant employees are aware of the news in time to change?
- Can timely know the news, we have our own exchange group, timely communication, it is not will be notified by telephone.
2, we have adopted a way of determining what is "delayed" and "must be achieved" feature?
- It determined according to the actual situation.
3, the project's export conditions (Exit Criteria - what "done") have a clear definition of it?
- Can run smoothly, there are no obvious bug, later gradually improved.
4, for a possible change whether contingency plans?
- Can, in time to support the rear end of the front end.
5, whether employees can work unexpected efficiently handle requests?
- Time off under the circumstances, it can be solved.
6, What have we learned? If history all over again, what would we do to improve?
- Make contingency plans.
Design / implement (4 minutes)
1, designed to operate at what time and by whom done? Is the right time, the right man?
- Designed by the team leader completed after the end of the division of labor, it seems the time is right, is the right candidate.
2, the design work have not encountered ambiguous situations, how the team is resolved?
- Font selection when there are differences, resolved by voting.
3, the team whether using unit testing (unit test), test-driven development (TDD), UML, or other tools to help design and implement? These tools work?
- Most of the tests are tests on HBuilder, very powerful tool.
4, 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 main part of the project UML documentation and the beginning of the same strain, some small margins modifications need to be updated UML documentation.
5, Bug What is the function of generating the most, and why? After publishing discovered something important bug? Why did not we think of these cases in the design / development time?
- Up to network requests Bug, data requests and data processing has brought us a lot of trouble. No important bug after release. These problems are unknown, for those of us who lack experience in the development can not be foreseen.
6, code review (Code Review) is how to proceed, whether the strict implementation of the code specifications?
- Time is tight and heavy task, failure to code review, also failed to strictly enforce the code specifications.
7. What have we learned? If history all over again, what would we do to improve?
- Splicing in the code, we need to waste more time to understand other people's code. Develop appropriate code specifications.
Test / release (3 points)
1, if there is a team test plan? Why not?
- There is a simple program, function of each module to be tested.
2, whether formal acceptance testing?
- Due to lack of experience, failed acceptance testing.
3, the team tested whether there are tools to help test?
- HBuilder built-in simulator to test.
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?
- Team does not currently have the capacity in this area.
5, which I found unexpected problems during the release of?
- No accident.
6, What have we learned? If history all over again, what would we do to improve?
- Develop detailed test plans, try to be specific.
The role of team management, cooperation (3 points)
1, how each team is to determine the role, is not the best use?
- By the head of distribution, truly the best use.
2, there is help each other what among team members?
- This is a must, everyone has their own blind spots, we solve many difficulties through mutual assistance.
3, when the issue of project management, cooperation appears, team members how to solve the problem?
- No matter what type of problem, the first step in the solution of our team is a team discussion, and then brainstorm to solve the problem.
4, each member represents a clear publicly thank the members of helpful (and write in their blog in):
- I feel Xiepei Rong helped me, because I am responsible for the interface short a rental car, I can not write, he would patiently explain, teach me, and API documentation, I'm not going to write, and he will be very patiently taught , I am also very happy to answer any questions asked.
5. What have we learned? If history all over again, what would we do to improve?
- Our team cooperation, timely communication to solve, the big question is not, in this regard, we are relatively good.
Summary: (3 points)
1, do you think the current state of the team belongs grade CMM / CMMI in?
- The initial level. Not by sound system drive the project forward, mainly by project leaders to follow up and assign tasks. In a major force in the development, the main person in charge of the project relies on the experience and ability, but he left a work order beyond recognition.
2, do you think the team is currently in its infancy / running / specification / create a stage which stage?
- On the run, under the specification, standardization of development or from a certain distance, our whole effort to advance standardization.
3, do you think this team compared to the previous milestone a milestone any improvement?
- Greatly enhance the team in the division of labor and collaboration.
4. What do you think most need to improve aspects is?
- Writing code for a predetermined specification.
5, the control principle of agile development, do you think your team is doing the best of which are several principles? Please list specific examples.
- Follow the rules of cooperation and achieve better success in the project: Team members collaborate to solve the problem through discussion.
- Steady work, there should be no outbreak of production: We set well in advance of scheduled tasks and development plans for each module to allow sufficient time.
- With simple faith, which is trying to reduce unnecessary workload of art. : Adhere to the principle of the development of simple, cut some of the sad features, documentation light, light flow, heavy output, weight goal.
Photos whole group discussion
Respondent summary
Team contribution
| member | Contribution ratio (%) | Division of work |
|---|---|---|
| Wang Yaoxin | 3 | Team planning, blog writing |
| Chen Chaoying | 3 | ppt, reply, compose blog |
| Chen Xiangyi | 20 | front end |
| Xupei Rong | 30 | Back-end integration |
| Tengjia | 7 | front end |
| He Jialin | 7 | front end |
| Shen Zi Yao | 3 | Demand report, ppt |
| Chen Zhirong | 7 | Front-end, ppt |
| Lin Galaxy | 11 | Back-end database |
| Fleming Town | 7 | rear end |
| Huang Hengjie | 2 | rear end |
This group scene plea score : 52.6
Other issues raised by the group
Electric vehicle driving violations who owns the responsibility
for this problem, several times in front of the defense has been said many times. First, we are not currently in place can not be banned manned to apply our software; secondly, we initially only for the great blessing of the campus market, the current campus electric car is very, very common human phenomenon; and finally, if really worried about this problem, we can choose short rental software module, you can own use alone, not manned.
Electric car is not with people, how to do the traffic police caught a fine of who is out
for this problem several times in front of the defense has been said many times. First, we are not currently in place can not be banned manned to apply our software; secondly, we initially only for the great blessing of the campus market, the current campus electric car is very, very common human phenomenon; and finally, if really worried about this problem, we can choose short rental software module, you can own use alone, not manned.
Interface can continue to improve in the beta stage, a series of high-level clean
good, thank you very much recommended.
How to ensure that electric vehicles for compliance?
Our driver authentication module to write a valid driver's license, the compliance of the electric car will have a driver's license, we later if time permits, consider increasing the upload driver's license and verification functions.
To solve the problem of how to load slow?
We will consider the optimization algorithm.
How do you and so many QQ number of task groups a platform to compete
and constantly improve their functionality of our software, to reduce the bug, with strength and love to win the customer's choice.
Interface can look better, a little ugly left fixed
first everyone's aesthetic is different, we are indeed relatively simple, the latter will be taken into account interface landscaping.
ID number simply limit the number of bits of real information it is still difficult to ensure effective, this how you solve it?
This is because of the tight schedule, so only a simple limit-digit ID number, the latter will improve this feature to improve security.
I learned own blood must say something, to do with the web app framework performance really is too silly, and if you really want to use the multiport unified syntax, but suggested a small program or flutter
good, thank you recommended.
Where the map interface to load more slowly, to consider whether the rate increase.
Will do.
Your application appears to use web technology to develop, ask what solutions using packaged into applications, and how the native system interoperability?
Using web-vue assembly, embedded html, made uni-app section, and then packaged into App, native operability can.
Personal section
- Personal PSP
| PSP2.1 | Personal Software Process Stages | Estimated time consuming (minutes) | The actual time-consuming (minutes) |
|---|---|---|---|
| Planning | plan | 30 | 30 |
| ·Estimate | • Estimate how much time this task requires | 240 | 480 |
| Development | Develop | 120 | 240 |
| ·Analysis | · Needs analysis (including learning new technologies) | 120 | 300 |
| ·Design Spec | Generate design documents | 60 | 60 |
| ·Design Review | · Design Review | 30 | 40 |
| ·Coding Standard | · Code specifications (development of appropriate norms for the current development) | 10 | 10 |
| ·Coding | · Specific coding | 240 | 300 |
| ·Code Review | · Code Review | 30 | 30 |
| ·Test | · Test (self-test, modify the code, submit modifications) | -- | -- |
| Reporting | report | 30 | 30 |
| · Test repor | ·testing report | -- | -- |
| ·Size Measurement | · Computing workload | 20 | 20 |
| ·Postmortem & Process Improvement Plan | · Hindsight, and propose process improvement plan | 30 | 30 |
| total | 240 | 480 |
- Individual learning progress bar
| N-Week | New Code (lines) | Cumulative Code (row | This week learning time-consuming (hours) | Cumulative learning time-consuming (hours) | Important growth |
|---|---|---|---|---|---|
| 1 | 91 | 91 | 8 | 8 | Learn to use prototyping tools |
| 2 | 408 | 499 | 14 | 22 | ai a partial implementation |
| 3 | 920 | 1419 | 70 | 92 | Plus modifications UI implementation ai |
| 4 | 60 | 1479 | 7 | 99 | Python framework of learning flask |
| 5 | 50 | 1529 | 3 | 102 | I did a little small micro-channel program |
| 6 | 595 | 2124 | 19 | 121 | Flask and use a database connection frame python, using uni |
| 7 | 223 | 2347 | 3 | 124 | use
|