Methodology

At Symphony Solution Indonesia we know it is not writing code that you are looking for, it's delivering solutions that work. Delivering solutions On-Time and On-Budget. One can have a very good pool of technical resources, but it takes a proven methodology to achieve the desired results. And that is what we have to offer.

We pride ourselves in having a methodology that will result in you having your solution On-Time and On-Budget.

An approach that stands the test of time


The Symphony Solution Indonesia approach is based on "planning while building", meaning planning should occur continuously as requirements and technology evolve. It utilizes our principles such as: risk-driven scheduling, a fixed release date mindset, activity based planning, visible milestones, and small teams. In contrast to top-down methods, projects are not driven by a waterfall model, but instead follow an iterative process model.

The development framework


At Symphony Solution Indonesia, we have chosen to follow the Microsoft Solution Framework Process Model to support our commitment to reliable, repeatable, customer centric, quality systems. The process model is a milestone based model that provides guidelines on planning and controlling results-oriented projects based on their scope, assigned resources, and schedule. It is an iterative and adaptable model with defined critical milestones, explicit team accountabilities, risk assessment built into the model, defined variables and priorities that affect scheduling, features, and trade-off decisions.The process model is characterized by emphasizing vision/scope rather than requirements, having milestones that are customer driven, rather than development oriented, and using versioned releases rather than including every feature the first time. The process model consists of four phases: Envisioning, Planning, Developing and Stabilization. Each phase culminates in a major milestone.

Envisioning phase
The project team is assembled to define the product, and articulate the ultimate goals for the product in a Vision Statement. The Vision Statement provides clear direction for the product. The scope of the product is also defined, providing the limits for a particular version of the product, recognizing that further development may come in future versions. This phase of the project culminates in the Vision/Scope Approved milestone.

Planning phase
Planning is when customers and the team agree on what to deliver and how to build it. This is an opportunity to reassess risk, establish priorities, and finalize estimates for schedules and resources. This phase culminates in the Project Plan Approved milestone. The project plan includes the functional specification and a schedule.

Developing phase
The approved functional specification and project plan provide the baseline for focused development to begin. The development team sets a number of interim delivery milestones, each of which involves a full test/debug/fix cycle. This phase culminates in the Scope Complete/First Use milestone. At this milestone, customers and the team, assess the product's functionality and verify that rollout and support plans are in place. All new development is complete and deferred functionality is documented for the next release.

Stabilization phase
In the Stabilization Phase, the focus of the team changes from creativity and finding elegant development solutions to rigorously and thoroughly testing the operational requirements of the product/system. Testing activities are performed concurrently with code development. Bug finding and fixing becomes the primary focus. The product is formally turned over to the operations and support groups. This phase culminates in the Release milestone.

 

 
© 2017 Symphony Solution Indonesia
Joomla! is Free Software released under the GNU/GPL License.