The Agile Approach
The Agile approach is designed to deliver better, potentially quicker solutions through the iterative development of small, workable pieces of code.Ē We all know that!
The Agile Sprints that focus on small subset of features and functionality, and may make some changes to previously delivered pieces. Such a different approach requires a smarter and efficient project management.
So what requires attention!
|Individuals and interactions over processes and tools|
|Working software over comprehensive documentation|
|Customer collaboration over contract negotiation|
|Responding to change over following a plan|
A simple, customer enticing, rapid development environment that will iteratively focus on your CHANGING NEEDS and will ADAPT as required.
What you get out of our approach:
|CONTROL over BUDGET|
|Control over the schedule and scope of project|
|Real time visibility and risk management|
|Easy change of requirements after the analysis phase|
|Concrete feedback on a regular basis|
|Faster rollout times for your solutions|
Every project at UG Software starts with pre sales. We often receive most client requirements in one of the following forms:
Case1: Low level specifications with specific deadlines
Case 2: High level specifications with or without deadlines
Case 3: Very crude: Need a solution similar to something
If itís Case1, we generally honor the RFP within 3-4 working days for a mid-sized software development project. If there is a requirement that based on some new technology or something we havenít touched earlier, we inform our client about the same and the delay it could cause in providing the quote/proposal.
There are two ways of moving ahead with Case 2. Within 4 working days, we provide a quote / proposal based on our understanding of things. We inform the client that this quote / proposal may however lack some finer details and so the price quoted must be considered ballpark as against the proposal. Such quotes often require a deeper review later on. We do not provide an immediate proposal/quote but send a list of questions to the client for further clarifications. This communication could be several rounds depending on the complexity of the project. Once we have nailed the low level details, we send a quote / proposal to the client.
For case 3, we insist the client provides some more details. We have our project questionnaires which give us good idea about client requirements and we can take it from there.
Scope docs are made for every project however small or big it may be.
A Scope document describes the project from three perspectives:
|Flow: Each userís activities on the application are documented in a sequential order. This is important and helps developers in creating use cases prior to development.|
|Sections: The whole application is categorized into functional modules and each module is a section. All the possible comps/user interfaces under each section are listed in a tree structure.|
|Functionality: Each section (including comps) is described to detail of every field.|
|Need/time required for creating low level documents|
|Third party response time|
|Client Feedback delays|
|Level of documentation required|
Technologies Pvt. Ltd.
|A-164, Sector 63, Noida
U.P. - 201307, India
| +91 120 4207206
+ 1866 760 1856