
Our client relationships aren't based on dependency. They are founded
instead on trust and mutual benefit. We transfer knowledge, make clients
autonomous, and solutions self-sustaining.
|
|
Why us - -> our IT methodology
Radicle’s Development Methodology forms the basis of our approach to software projects. It
relies on five basic phases – Define, Design, Build, Test, Deploy. Contrary to traditional
approaches and consistent with our emphasis on flexibility, the development methodology does
not mandate specific tools and technique that should be used within each phase. Rather, the
focus is on ensuring that the goals and deliverables of each phase are met. We tend to be
very careful in the tasks and activities we perform.
Our Functional Specification and Technical Design documentation is very focused,
targeted towards right audience and with the goal that knowledge transfer
can be achieved without noticeable effort - thus making solutions self-sustaining and clients autonomous.
Our consultants have significant, real world experience with many different techniques – traditional
waterfall development, SCRUM, Iterative development, UML based approaches, agile approaches etc.
The choice of specific tool and technique is based on project goals and client needs.
That is, we will work with you to decide what makes most sense in your environment.
After all, the goal is for your team to manage and support the system once development is
completed!
| Define |
- The objective here is to finalize the solution vision and
'what' are the specifications of the system.
- Main deliverables are Strategic Analysis, Business Function
Specification and User Experience Interface.
- The intended audience of the documentation is someone with
business focus.
|
| Design |
- The objective here is to finalize 'how' the system is going to
be built.
- Main deliverables are Technical Design, Html Templates and
Test Plan.
- The intended audience of the design document is someone with
technical focus.
|
| Build |
- The objective here is to build the system complete with unit
testing.
- Main deliverables are system code, system operation document
and user training material.
|
| Test |
- The objective here is to complete the system test and user
acceptance test.
- Main deliverables are executed test plans and production ready
system.
|
| Deploy |
- The objective here is to train the users and deploy the system
to production.
- Main deliverable is live system.
|
|
|