Some of the agile practices such as pair programming often are harder to sell to industry than others. Most team development projects seem to employ some agile practices, but not others.
I do quite a lot of pair coding, specially if it's a very important/high impact or complex feature that we want to get right down to the last detail, two brains think better than one and the time we focus when working together is longer. we get a lot more high quality work done this way.
tried doing the standup meetings, but never got used to them.
not sure if this is part of agile, but we just iterate and release in short periods. release early, release often.
We did a case study of agile practice experiences at Cordys software development. The paper "Getting Agile Methods to Work for Cordys Global Software Product Development" describes to what extent they use agile practices and their experiences
Pair programming is part of XP and maybe any other Agile method it's very helpful for us but not easy to use, cause it's hard to know when to use that and when not to use that.If you use this method on non important part of code u lose time and spend more money for nothing.
We try to do the full scrum process and use AgilZen as support.
We basically use sprint of 15 days.
We then are doing the standup meetings (Daily Scrum), Backlog grooming, Sprint planning meeting and of course, Sprint review meeting.
We try to get as much feedback from shareholders as possible.
But in software and codec development we don't have so much deliverables.
For the past four years we have been using Crystal Clear process, and we are very happy with our outcome. We are currently using this process on a major project for Federal Aviation Administration.
- Badges
- Science topic
- Similar topics
- Computer Science