WESCO Logo

WESCO HELPcycle™

The HELPcycle methodology is the set of best practices that facilitate timely completion of a project. The premise of the WESCO methodology is that software creation is a science rather than an art-type activity. This science relies on the steady performance of a team applying standard processes to produce predictable results. Today many organizations survive on the completion of high-risk projects. Industry-wide reliance on personal heroics, outdated management practices, and outdated software creation practices consistently cause such projects to be completed late or not to be completed at all. HELPcycle is sufficiently comprehensive to ensure timely completion of these large, complex, high-risk projects that frequently involve:

  • Multiple delivery units, subcontractors, vendors, customer personnel, and interfacing entities, all of whose activities must be effectively organized and coordinated.
  • Multiple technologies such as LAN, WAN, Client/Server architecture, imaging, and multiple-platform production environments.
  • Multiple contracts for software, hardware, tools, and services such as business analysis, software development, training, communications, and installation, all of which must be synchronized within a vision of the project that meets customer requirements and is acceptable to all participating vendors and customers.
  • Geographically distributed project teams where critical project activities are performed in multiple locations, often by multiple companies.
  • Multiple user communities in geographically distributed locations.

The HELPcycle methodology is scalable, and consistent application ensures completion of all projects regardless of size or complexity.

Click here to download a complete copy of the WESCO HELPcycle™ document (PDF 124KB).

The links below will take you through an online tour of the WESCO HELPCycle™ document.

HELPcycle™ Software Development Process
HELPcycle™ Phases
   Analysis and Planning
   Design
   Software Development
   Training
   Implementation
   Acceptance
   Maintenance

Capability Maturity Model

<< Back >>