My first Agile post-its
My current project is beeing managed in Agile Software Development.
I must admit that I was quite a little suspicious but my first steps are positive.
The main point, as part of the Game Team, is that i know far more about the activities of my collegues: it’s a Team Play. During the Stand-Up Meeting, everyone talks about his work yesterday and his plans today. It’s the moment to communicate on your trouble, most of the time others met them too. Usually, you are working on a functionality close to your collegue next door and you don’t even know. Or maybe you have a brillant idea that may interest. Anyway, your daily work is clear for the team. So, priorities can be followed.The development team follows “as much as possible” the Extreme programming best practices as Continuous Integration, Test Driven Development, Pair Programming, Design Patterns.
But I have also discovered some limitations. The functionnal specifications are divided in pieces into greenpeppers. Therefore, it is hard to build a global specification interpretation and get into the project.
Key Words: Greenpepper, Hudson, Checkstyle, Cobertura, PMD, FindBugs
February 25th, 2010 at 12:02 pm
Yes, i agree with you,
The main problem and limitation is the lack of knowledge of the functional goals.
You have a very short description of what you have to do, and you don’t know what the future will be. So, you can not anticipate , and you are sure you will have to “refactor” what you have done .
It is sometimes hard to know exactly what “they” want !
It may be sometimes , a lost of time …