Information
Our Approach
|
You and your business are important to us. We work with you and for you to find the best solution for your business need according to your budget contraints. We think long term and holistic. When we deliver systems, it is what you need when you need it. We use the Agile methodology whenever possible. This approach ensures collaboration in every step of the project life-cycle and makes sure that the development team does not lose sight of what you as a client need. |
The principles of Agile are:
- Frequent Delivery
- More Iterations
- Test frequently
- Less defects
- Collaborative approach
- Scrum
- Extreme Progamming
Scrum
Each iteration would called a scrum with a fixed deadline which can be a 1- 2-Month period. With this method the Client prioritise his requirements to indicate what he wants in place first.
Extreme Programming (XP)
Each iteration here is typically shorter than a scrum - maybe 2-4 weeks. Here the developer prioritises what to do first on the basis of the client requirements.
Agile Methodology
Agile methodology is an approach to project management, typically used in software development. It helps teams respond to the unpredictability of building software through incremental, iterative work cadences, known as sprints. But before discussing agile methodologies further, it’s best to first turn to the methodology that inspired it: waterfall, or traditional sequential development.
Why Agile?
Agile development methodology attempts to provide many opportunities to assess the direction of a project throughout the development lifecycle. This is achieved through regular cadences of work, known as sprints or iterations, at the end of which teams must present a shippable increment of work. Thus by focusing on the repetition of abbreviated work cycles as well as the functional product they yield, agile methodology could be described as “iterative” and “incremental.” In waterfall, development teams only have one chance to get each aspect of a project right. In an agile paradigm, every aspect of development — requirements, design, etc. — is continually revisited throughout the lifecycle. When a team stops and re-evaluates the direction of a project every two weeks, there’s always time to steer it in another direction. The results of this “inspect-and-adapt” approach to development greatly reduce both development costs and time to market. Because teams can gather requirements at the same time they’re gathering requirements, the phenomenon known as “analysis paralysis” can’t really impede a team from making progress. And because a team’s work cycle is limited to two weeks, it gives stakeholders recurring opportunities to calibrate releases for success in the real world. In essence, it could be said that the agile development methodology helps companies build the right product. Instead of committing to market a piece of software that hasn’t even been written yet, agile empowers teams to optimize their release as it’s developed, to be as competitive as possible in the marketplace. In the end, a development agile methodology that preserves a product’s critical market relevance and ensures a team’s work doesn’t wind up on a shelf, never released, is an attractive option for stakeholders and developers alike.