Effective processes are essential in order to ensure high-quality results. ITWorx methodology defines three specific process areas.

Requirements Management

Nowhere does our agility serve us better than in Requirements Management. We realize that in today's rapidly changing business environment, requirements are constantly evolving. Be it a change in market conditions, a new announcement by the competition, or simply a better understanding of the problem at hand, change happens. The long-standing practice of freezing a rigid set of requirements at the beginning of a project is no longer valid – if it ever was. Data collection, analysis, and translation into requirements is a continuous process running throughout the lifecycle of a project. We recognize this need to be flexible, and have mastered the art of balancing inevitable changes to requirements, with the discipline and rigor needed to bring projects to completion.

Software Development Life Cycles (SDLC)

Adopting an SDLC is basic. Adopting the right one is critical. Whether classic Waterfall, spiral waterfall, rapid prototyping, Rational Unified Process, Rapid Application Development, or Extreme Programming, choosing the right SDLC is often the most important early decision in a project. Choosing the wrong SDLC can often lead to disaster. Once chosen, we continuously monitor the project for SDLC-related problems and quickly act to modify or replace an SDLC that is no longer appropriate. We typically apply three different sets of criteria when selecting and tailoring the SDLC best suited to the business problem at hand.

Project-based Criteria: No two projects are the same. We examine project characteristics such as type of project, size, complexity and expected duration, as well as properties such as industry maturity, expected requirement churn, and required reliability to determine how to best select and tailor an SDLC for your project.

Customer-based Criteria: We can tailor our SDLC to fit a customer’s particular needs. Specific reporting requirements, project visibility requirements, organizational buy-in, and other considerations can all be accommodated.

Team-based Criteria: The project team's familiarity with the domain, technologies, and tools, and the team’s geographic distribution as well as the involvement of third-party suppliers or contractors are all important team-related factors that can influence the choice of SDLC.

Configuration Management