|
Agile development Principles |
Our approach |
1 |
Early and continuous delivery of valuable software to meet customer needs |
The software is temporarily incomplete, but some documents have been delivered and can be used to interact with the user through the document. |
2 |
Welcome changes in demand and use this change to improve the user's competitive advantage |
Ask your classmates or think about yourself to see if you can make college students satisfied. |
3 |
Frequent release of available software, the release interval can be from a few weeks to several months, short or short |
Since our project requires delivery within one months, we do not deliver the software, but we make a weekly design document that explains the project and the progress of the process. |
4 |
Business people and developers should work together every day during the project development process |
Because it is a college student, so we will exchange in this class, if necessary, we will be in the spare time to Exchange online, together to discuss the project completed the process of problems. |
5 |
With enterprising people at the core, full support to trust them |
Our team leader itself is a very good person, she usually to their own requirements are more stringent, in the minds of students also have more prestige. And our deputy team leader is also a technical strongman, in the course of the whole project, he is responsible for technical guidance, so that everyone is very motivated. |
6 |
In-person communication is always the most effective way to communicate, both inside and outside the team |
Throughout the development process, our entire team is divided into groups, each with its own work, each with face-to-head interaction. |
7 |
Available software is a key indicator of the progress of the project |
In our team, all members use Eclipse for development. |
8 |
Agile processes should be able to maintain sustainable development. Leaders, teams and users should be able to continue to work at the current pace |
Because the project is still at the completion stage, this part is not included in our consideration. |
9 |
Only with constant attention to technology and design can we become more agile |
In the process of carrying out the project, we continue to learn new technology, but also constantly self-reflection, to improve the design of software. |
10 |
It is important to keep it concise and to simplify the workload as much as possible |
As far as possible to streamline their own system, remove redundant functions, so that the system screen concise. |
11 |
Only self-managing teams can create great architectures, requirements, and designs |
Complete the scheduled tasks in time every week, in the completion of the task, but also to summarize deficiencies, propose improvements, and to implement these improvements. |
12 |
Always summarize how to improve team efficiency and put into action |
This is what we did not do, I will propose to the team leader, often to summarize the work of the group, and to members of the announcement, so that we can learn from each other, improve team efficiency. |