Rainbow reflection community work summary
Sichuan Normal University: Li Wei
Sichuan Normal: Liao snow
Southwest University for Nationalities: Week Ogawa
Guilin Institute of Aerospace Engineering: Liu Jianhua
table of Contents
1. Team Concept
2. sprint reflection meeting
3. Specific reflection
4. The task burndown
1. Team concept
I am a slow walker,
but I never walk backwards.
Those fine and beautiful existence will not disappear,
It is still warm memories of appearance;
Toward the sun, Dianqi arch,
Stumbled strong,
Stumbling growth;
- prototype development team of seven colors reflect community management project
2. sprint reflection meeting
After Alpha iteration, all members of the team held the first round of the sprint will reflect. All members take turns to speak, to reflect on the current round of sprint existing problems, improve simultaneously into the next iteration.
Reflection maps summarize as follows:
3. Specific reflection
1 , lack of demand for design
Projects by watching other groups, we reflect on the project in determining demand needs to understand is not in place, needs analysis inadequate. Only preliminary understanding of the business community management, lack of experience in the field of business management student organizations. Only consider the basic needs of the business community management, without taking into account some of the regular features of mobile business applications, such as point of praise, attention, circle of friends and forwarding social networking features.
Solution: Find information through the network, brainstorm with each other in the panel discussion.
2 , prototyping tools inexperience
Some members of the team for the first time prototyping tool blade, lack of experience, although the first day blade of technical support staff to help guide the use, but for some special features not familiar with, later also need more practice, and more practice learning paradigm provided by others.
3 , agile development emphasize the ability to adapt quickly to changes in demand
Team members through prototype development and design of the project, the initial experience the ability to adapt to agile development of rapid changes in demand, experience tells us that in actual initial division of tasks, the project manager should take into account the cost of learning new software engineering tools and develop work plan, otherwise it will lead to deviations from the expected time of the initial burn.
4 , about the silver bullet
在佛瑞德·布鲁克斯于1986年发布的《没有银弹：软件工程的本质性与附属性工作》这篇软件工程的经典论文中，作者向我们讲述了软件工程没有银弹这样的理论。银弹，指的是强有力的武器。用作者的观点来说，就是：“软件工程中不存在银弹——没有任何一项技术或方法可使软件工程的生产力在十年内提高十倍”。软件创作包括本质性工作和附属性工作。本质工作指的是软件构建、软件从抽象性问题发展出解决方案。附属工作指将解决方案实现到电脑上所遇到的困难。文章中说，附属性工作将会随着工具的改善而逐渐淡化，并举例说明从汇编到高级语言，附属性工作难度的降低使软件开发效率大大提高。我认为这一点很正确，附属性工作会随着软件行业整体的进步逐渐降低。近年来开源流行，许多先进技术的开源，框架的开源，都给我们软件开发提供了非常现成的工具。通过工具的帮助，我们对于软件的想法可以很快实现。软件设计中重复的工作可以交给“工具”来完成，而本质性工作的复杂性则难以消减、淡化，并始终制约软件开发效率，使得软件开发没有“银弹”。这些本质性的工作包含复杂性、一致性、可变性和不可见性。通俗地讲，这些复杂性的难度表现在如下几点：
（1）软件功能的增加，会导致软件在复杂性处理上付出的设计成本几何级增长。
（2）软件工程从来不是一个人的工程，有时也不是一个开发团队的工程，这里面接口、文档、以及设计的一致性直接影响开发效率、沟通成本的高低、大小。所以一致性必不可少，而软件各模块一致性的设计是相当复杂困难的。
（3）软件的首要功能是服务用户，因此经常会需要持续变更，保证软件的可扩展性也是软件设计中的本质工作之一。
软件工程没有银弹，但却有各种增加软件开发效率的方法。
4. 任务燃尽图
