Summary to RapidFTR project

原创 2010年12月03日 00:47:00

Wang Xia and I have been on RapidFTR project in these two weeks (Nov. 22 ~ Dec. 3).

We kept participating in the standup meeting at 11 a.m. every day. We picked the stories from both the Blackberry side and web application side. We often worked as QAs too, testing the program and reporting bugs in the group.
We have been kept a good relationship with other collaborators. We discussed the tech problem with other Devs(like Zabil) and acceptance criterion with the BA/Customer (like Jorge). We believe they have got a little impressed by our voice and serious work.

In this two weeks we learned a couple of things from this project.

Diversity:
Collaborators from different countries have their own situation every day and can't have a tight connection with others. In addition, the project happens to be a social one, and team members usually did not promise their velocity in iterations. So, we have been used to notice someone "disappeared from the world" for a long time, and sometimes with bad luck, we happened to need them at that moment but couldn't find them in any way.  

Collaboration:
At the beginning, we should introduce the tech level of ourselves to the team and announce which kind of stories we can do. That's important for team to know each member. The second is the skpye standup meeting. Everyone should tell his comments to the work he did yesterday and let others know his plan which story would be picked. The customer will concern based on one's story and the pm will know how it is going on for every contributor. The last thing here is the most common one, communication. Ask your questions, tell your concerns or comments and listen to other peoples' saying. Do these in time, professionally and friendly.

Open-source:
We learned how they organized the source of the project. They put a resource list on the github, telling where we can get the instructions for setting up environment, code repositories and Mingle site, etc. That's really helpful; As developers, to edit the code is the basic thing we must do to make the contribution. They use github as the code base which is quite popular in this kind of open-source project. There are two ways for us to check out and in the code. One is to ask the code owner to add our github account as a "collaborator" in his repository. Then we can get the read+write privilege to his code repo. The other is more common. We can fork a repository for us on github from the owner. Every time we update the code from the owner's repo and commit changes to our own repo. Then we send a pull request to ask the owner to fetch our revisions and do the merge.

Technology:
This project has two parts. One is for Blackberry using Java language and BB simulator, the other is for web application using Ruby on Rails. We learned many tips of writing Java code under the specified JDK by BB, and how to test and debug the app with BB simulator. We also increased the knowledge for the environment and development of Ruby on Rails. Especially, we learned some new things, like the test with Rspec and Cucumber, which is related to Behavior Driven Development (BDD).

 

The project will have a release after this week and many teammates had announced their leaving. Maybe we will leave too, or maybe we will stay. You never know it when you are in ThoughtWorks. :]

Stealth Project Summary

public class Tags : MonoBehaviour {public const string player = "Player"; public const string siren ...
  • googtiki
  • googtiki
  • 2017年11月18日 20:17
  • 27

Learning project summary

CSDN is the personal network where you can share privately with the people who matter most. ...
  • chenhaiming123
  • chenhaiming123
  • 2017年08月25日 21:47
  • 176

Summary for maven project

1,If there is no jar files can be found in the specific folders,how to add jar file manually.mvn ins...
  • CodeCompiler
  • CodeCompiler
  • 2015年06月15日 09:28
  • 237

项目总结- Summary of project

Summary of Documentation in CertificationIn certification project, the task of our team is mainly in...
  • chengkeke
  • chengkeke
  • 2005年10月24日 15:02
  • 857

Summary of G603 Project

Take part in the G603 project about three months. In these days, I was learned a lot, thanks to my c...
  • fendouzhe_wupeng
  • fendouzhe_wupeng
  • 2012年07月24日 20:55
  • 165

代码和编辑器中的/// <summary>/// </summary>有什么作用?

 也是一种注释,但是这种注释主要有两种作用: 1。即是上面大家所说的这些注释能够生成一个XML文件。这样呢看起来会对程序的内容一目了然。 2。以这种方式对你的类,属性,方法等等加上注释之后,...
  • Sara_xie
  • Sara_xie
  • 2015年05月29日 16:35
  • 721

C# 显示注释 Documentation summary

XML Documentation in C# Anson Horton, C# Compiler Program Manager C# supports the creation of XML ...
  • csdnbao
  • csdnbao
  • 2011年10月08日 21:04
  • 1687

IOS NDDictionary使用中value遇到no summary如何判断为NULL

直接上代码,判断value是否为null的方法。 -(BOOL)isNull:(NSMutableDictionary *)dict key:(NSString*)key{ // judge...
  • JJMM2009
  • JJMM2009
  • 2017年04月12日 14:13
  • 1252

C#中的<summary>

初学C#,看公司代码的过程中一步一步学习,现将学习过程中发现的一些知识总结整理出来,无论难易,以供后续不时之需。 在C#中, 标记应当用于描述类型或类型成员。 使用  添加针对某个类型说明的补充信...
  • a364416036
  • a364416036
  • 2016年07月20日 11:44
  • 3413

Android Studio教程04-导入Eclipse项目到AndroidStudio(包括导入第三方Project项目(不是jar包形式))

1、在Welcome界面选中Import Project(Eclipse ADT, Gradle,etc) 在第二个界面选中自己的Eclipse项目。 ...
  • q908555281
  • q908555281
  • 2015年09月11日 17:45
  • 1588
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:Summary to RapidFTR project
举报原因:
原因补充:

(最多只允许输入30个字)