Agile Development Methodology
Many companies state that they follow Agile development rules, but there are so many ways to develop per the Agile method, so what does that really mean.
What it is: When dealing with distributed development, one common issue for companies is that they often have the feeling that they are not sure what is going on way over there, are those people really working, what are they doing. Do we just throw something over the wall and hope in three or six months that they get what they asked for. Following an Agile development methodology helps alleviate this risk for companies. In particular Softjourn stresses:
- Constant customer interaction;
- Frequent deliverables.
In this way you will continually see what you are getting, will continually know what is going on, and be able to provide feedback.
How we do it: But it is not enough to say that you work in this manner, you have to really live it and prove it. Here is how we prove it:
- For a project of less than a month, minimum delivery of every four business days;
- For a project longer than a month, minimum delivery dates of weekly;
- The first phase of every project is a design review/design development phase which includes daily communications, the actual length of time of this phase depends on the length of the project (can vary from 1 day to 5 days).
Building Trust: Frequent deliverables and communications help to build trust in a distributed environment. We start to earn your trust by initially delivering daily what we say we are going to deliver, then every few days, then weekly as the project progresses.
Agile development can be used for all sizes of projects; from pilot projects through multi-year projects. Each project is unique and has its own rules. Whether it is a pilot project or a multi-year project, a specific plan is developed for that project alone.
The Agile Software Development Manifesto we live by!
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more