We follow agile methods and principles, and bring success for any kind of business and engagement contract. We are expert with agile methods and curious about our take on agile software development.
There are many agile methods available, of which we find that Extreme Programming and Scrum are the two methods that are best suited for us to provide you the maximum benefits. Any one of these methods alone has inherent drawbacks. So we have adopted a hybrid method by blending the benefits of both. This page explains how we work through the agile methods.
The Agile Manifesto provides very broad guidelines:
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.
Agile Manifesto »
The manifesto is about what gets priority, not what gets done.
That said, here’s how we put these guidelines into practice:
As software developers, we are actually passionate about tools. And we love our processes as well. Both processes and tools help us get things done.
But tools and processes can get in the way of people and relationships. This principle guides us in choosing tools. We choose tools that amplify the individual’s effectiveness, rather than tools that the person has to steer and control. And we choose tools that facilitate collaboration and communication.
At Agile Codex, we keep software working and ready to ship throughout the development lifecycle by:
In software development, documentation is important, but, exhaustively documentation of everything is expensive. The software itself suffers from the effort devoted to expensive documentation. So, we don’t write documentation fully for every project upfront; we write documentation when it is needed and has value. Our tools and processes help us to prepare documentation effortlessly in most of cases.
We follow different Requirement Engineering techniques which help to prepare the SRS documentation quickly. That specs are designed for skilled programmers, also understood and verified by our customers. Though we write documentations, we exhibit the part of working software even in first iteration.
We believe good UI design reduces the importance of user manual.
We follow sustainable techniques and processes to prepare technical documentation even in little efforts. That documentation helps future developers to understand how to fix, maintain, and extend the software.
We like to work in iterations so that we can deliver working software to the customer every week. If there’s some external reason that they need to cut the project short, they will have still received something valuable.
For any business and engagement models, we have track records of successful projects using agile methods. As our developers and scrum masters have over one and half decades of experience in software development, we understand the big picture clearly. So, business collaboration and negotiation are followed by the contract.
At Agile Codex, the following practices help teams respond quickly to change:
The principle doesn’t devalue planning—just sticking to the plan. Planning is valuable in itself, and because the plan helps us recognize when things have changed; it helps us understand the implications of change, how we need to adjust, and the likely cost. The important thing is that, as we make plans, we understand that the plan may have to change. Planning is an ongoing time-boxed activity that includes