HomeServicesCustom-made development
Guided by our goal of satisfying our clients’ needs and offering a high quality product we are in the process of certifying ourselves in ISO 9001. Apart from this, all our developments are done using well-known international methodologies such as SCRUM and UP.
We strongly believe that the key to successful tailor made software is the methodology used.
The Up Methodology:
The Unified Process is a traditional “cathedral” style of incremental design driven by constructing views of a system architecture. It has the following key features:
- It is component based, commonly being used to coordinate object oriented programming projects.
- It uses UML - a diagrammatic notation for object oriented design - for all blueprints.
- The design process is anchored, and driven by, use-cases which helps keep sight of the anticipated behaviors of the system.
- It is architecture centric.
- Design is iterative and incremental - via a prescribed sequence of design phases within a cyclic process.
Phase 1 Gathering information and Requirements
Phase 2 Time Scale and Iteration Plan
Phase 3 Technical Analysis – Database Design and UML Diagrams
Phase 4 Programming and constant testing – Beta Version
Phase 5 Further Testing for Final Version
SCRUM:
Scrum is unique because it introduced the idea of “empirical process control.”
Scrum uses the real-world progress of a project — not a best guess or uninformed forecast — to plan and schedule releases. In Scrum, projects are divided into succinct work cadences, known as sprints, which are typically one week, two weeks, or rather short in duration. At the end of each sprint, stakeholders and team members meet to assess the progress of a project and plan its next steps. This allows a project’s direction to be adjusted or reoriented based on completed work, not speculation or predictions.
Scrum has three fundamental roles: Product Owner, ScrumMaster, and team member.
-
Product Owner: In Scrum, the Product Owner is responsible for communicating the vision of the product to the development team. He or she must also represent the customer’s interests through requirements and prioritization. Because the Product Owner has the most authority of the three roles, it’s also the role with the most responsibility. In other words, the Product Owner is the single individual who must face the music when a project goes awry.
The tension between authority and responsibility means that it’s hard for Product Owners to strike the right balance of involvement. Because Scrum values self-organization among teams, a Product Owner must fight the urge to micro-manage. At the same time, Product Owners must be available to answer questions from the team.
-
ScrumMaster: The ScrumMaster acts as a liaison between the Product Owner and the team. The ScrumMaster does not manage the team. Instead, he or she works to remove any impediments that are obstructing the team from achieving its sprint goals. In short, this role helps the team remain creative and productive, while making sure its successes are visible to the Product Owner. The ScrumMaster also works to advise the Product Owner about how to maximize ROI for the team.
-
Team Member: In the Scrum methodology, the team is responsible for completing work. Ideally, teams consist of seven cross-functional members, plus or minus two individuals. For software projects, a typical team includes a mix of software engineers, architects, programmers, analysts, QA experts, testers, and UI designers. Each sprint, the team is responsible for determining how it will accomplish the work to be completed. This grants teams a great deal of autonomy, but, similar to the Product Owner’s situation, that freedom is accompanied by a responsibility to meet the goals of the sprint.