logo_1 HOME| CONTACT| LOGIN

Approach

Approaches, Styles, & Philosophies used at Primearrow

Formal methodsDue to the high cost of using formal methods, Primearrow uses these methods usually only in the development of high-integrity systems, where safety or security is important.
Programming paradigmA programming paradigm is fundamental and widely used by the company to define style of solutions offered in a programming language. Most widely used are Object oriented —Aspect oriented—rule based & Functional.
MethodologyMethodology is a style of solving specific software engineering problems; carried out to produce software.
Anti-patternsAnti-patterns are specific repeated practices that appear initially to be beneficial, but ultimately result in bad consequences that outweigh the hoped-for advantages.

Approach to Methodologies in Software development. Primearrow deploys current state of art methodologies like
• Agile, Scrum, 7 principles of Lean software Development to achieve targeted ROI on various development projects.

Agile/Scrum

Agile development, in its simplest form, is a lightweight framework which helps teams, given a constantly evolving functional and technical landscape, maintain a focus on the rapid delivery of business value. As a result of this focus and its associated benefits, capable of significantly reducing the overall risk associated with software development. Agile development accelerates the delivery of initial business value, which is maximized throughout the development process. As a result of this iterative planning and feedback loop, teams are able to continuously align the delivered software with desired business needs, High Adaptability to changing requirement scenario is ensured. Agile software system addresses the business and customer needs in much better manner.

Developmental Value Proposition:

Agile methodology increase
ADAPTABLITY,
VISIBILITY,
BUSINESS VALUE,
and reduces considerably the risk factors

Development Process

A classical project charter will describe theories and responsibilities of the key personnel, so in Agile process we simply insert Scrum as the development tool. It is helpful to recapitulate the essential points to be included in Agile specific practices:
• Product Owner and Scrum Master and who will provide them
• Sprint Planning & Demo Meetings
• Burn Down Charts
• Additional metrics (test burn up charts)
• Escalation procedures
Scrum itself does not define relationships beyond the Scrum team. So we include a "Management Oversight Committee" modeled on Enterprise Transition Team. This should be an effective alternative to a steering committee. The MOC would meet (at least by phone) regularly and resolve impediments raised by the Scrum Master.


SW Development principles adopted by Primearrow.
Eliminate waste:-

Use of Lean methodologies will eliminate wastes, not costs. it is one of the most important principles of Lean Software Development. Primearrow development team strives to produce the best products and to deliver only features that are of paramount importance to their customers. New research confirms 20% of functionalities represent 80% of the value of the product. This criteria could apply to all types of enterprises — Lean methodology eliminates all unnecessary steps and waiting periods; Developer should strive to get the value as soon as possible and ensure to derive pure value without any waste.


Create Knowledge:-

Inherent weakness of humans is to ignore learning from their past mistakes, software developers are not akin to this same rules apply to the software development teams – it′s much easier to work in an environment that encourages you to learn and to create knowledge. Why should you create knowledge? Knowledge base wills eliminate repetition of mistakes by implementing teams, and save value time and effort. It′s much better and safer to learn from someone else′s mistakes


Build Quality in:-

In most cases QA team gets the product after it has been implemented and this is the root cause of all issues. Traditionally QA is considered as a separate entity in software industry, this approach is proved to have many disadvantages. Companies should care about quality from the day one, before writing a single line of code. Software teams should "build quality in" their products and QA should not be considered as a separate activity. Quality Assurance should be constant process of improving the product - QA activities and people should be involved in the development of the product during the development, not after when the developers are moved to another project.


Defer Commitment:-

No matter who you are, where you live and what your job is you have to make Decision making is not always easy for the project leaders. Lack of solid information & data hampers the decision making process. In this principle decisions are made in the last moment with solid build of information in hand which ultimately eliminates poor decision making. But it is not procrastination, surly.


Optimize the Whole:-

Optimizing the whole project components instead of focusing on individual bits of the project, will enhance the total percentage of success-Primearrow follows this principle-indirectly enhance the total quality of the product.


Deliver fast with small packages:-

Small packages are easier to manage than the big one, you can expect Smaller amount of defects can be expected from , Small software packages, they are easy to manage & integrate. Six months without regular integration in the production environment will bring you much more problems. Defects discovered just before the release will make developers to fix by working overtime.


Respect People:-

People management in software development team is a real challenge, and giving Desired Respect each member of the team is a solution for this challenge.


  footermidline  

  footermid line  

  footermid line  

  footer mid line  

  Footer_midline  
Contact Us
PrimeArrow Inc,
43676 Trade Center Plz,
Suite 140,
Sterling, VA 20166.
Email:hr@primearrow.com.

Copyright © 2011 Primearrow. All rights reserved.

down_logo_1