© 2011 Ostiary
A better way to develop software
Our highest priority is to satisfy a customer through early and continuous delivery of software with business value.
We welcome and can manage customers changing their requirements, even late in the development phase. The agile processes harnesses change for the benefit of a customer giving them the necessary competitive advantage.
We prefer to deliver working software frequently, with a preference for shorter timescales.
We insist that business people and developers work together daily throughout the project.
Projects are completed by motivated individuals. So our goal is to create the environment and support needed, and trust the team to get the job done.
We believe that the most efficient and effective method of conveying information to and within a development team is by face-to-face conversation.
At the end of the day a piece of working software is the only measure of progress.
Agile processes promotes sustainable development rather than long hours and early burn out. Sponsors, developers, and users should be able to sustain and maintain a constant steady productive pace indefinitely.
A passion for detail and constant attention to technical excellence and design enhances agility.
We strive for simplicity by removing all unnecessary embellishments, hypothetical exceptions and by creating and maintaining a consistent architectural model
We believe that the best architecture, requirements, and designs emerge from the continuous ,open, honest and debated dialogues between team members .
We believe that every project team needs to stop , reflect and adjust their course from time to time
In order to succeed in the new economy companies have to embrace this new more realistic, pragmatic, non bureaucratic approach to software development. Too often projects are saddled with too much “non value adding processes”
The only processes that should be retained are those that help deliver something timely and tangible and "as promised" to a customer.
The Agile movement is not anti-methodology. Its core aim is restore balance between getting it done and the paperwork needed to support the work. Too many projects generate unnecessary documents that clog up and collect dust on corporate repositories
Modeling is essential but its main purpose is to express and understand business complexity. Requirements documentation is essential but should not be hundreds of pages long. Such lengthy tomes are never maintained and rarely-used.
Plans are essential but there are real limits to planning in a constantly changing turbulent environment.
© 2011 Ostiary