Methodology

Art and science have their meeting point in method.

Edward Bulwer-Lytton (1803 - 1873)

Web development is a combination of art and science. As is the case with the arts and sciences, method is critically important. Without a coherent method, a web development project cannot be efficiently completed. A web development project without proven methods behind it cannot be scheduled or budgeted with any degree of confidence. Without method, a web development project can only be completed on time and on budget by luck or coincidence. When it comes to web development, method is the difference between amateurs and professionals.

Design

Peak Systems' graphic design process begins with extensive research on our client and our client's industry, including peers and competitors. Studying our client teaches us the nature of their character, their image, their taste and how they choose to present themselves. Studying our client's peers and competitors teaches us the common visual language of their industry, revealing trends to embrace, clichés to avoid, and new avenues that are ripe for development.

Next, we deconstruct that visual language and reassemble the pieces, starting with fixed elements such as logos, corporate color palettes, and client preferences. We build a visual framework that emphasizes our client's unique personality, meets their technical needs, and communicates their message clearly.

Ultimately, design comes down to personal taste. It can be tricky satisfying both you and your audience. That's why we view this stage of design as an ongoing process that we use to discover your unique taste. With your feedback and guidance, we will refine our ideas until they meet your satisfaction.

Project Management

No matter how talented a development team is, the only thing standing between them and missing a deadline or going over budget is effective project management. We at Peak Systems pride ourselves on our project management skills. Peak Systems utilizes Project Management Institute (PMI) standards adapted to our consulting and business analysis role. Our adherence to these globally recognized standards minimizes the risk of problems caused by improper or inadequate planning in projects, helping us complete our projects on schedule and on or under budget.

Once a project is approved, a work plan will be agreed to with deadlines and milestones for deliverables from both Peak and our client. Peak will provide a project manager to serve as the central point of contact for communications for the duration of the project. The project manager will coordinate Peak’s resources as necessary to complete the engagement and serve as a liaison to the client.

Peak will provide a “client site” to serve as a central repository for collaborative communication between Peak and the client. The client site will be password protected and maintained by the Peak project manager. Items such as contact lists, links to proposed materials, documents, and the like will be available to project participants on the client site. The client site will be accessible via Peak’s website (www.peaksystems.com).

In the project kickoff meeting, contact lists will be exchanged between Peak and the client. Individuals will be identified as decision makers for various parts of the project. The client will identify individuals who have authority to give approvals, request change orders and hold various other roles for the duration of the project. This creates an environment where clear communication can take place and misunderstandings can be avoided as much as possible.

Development

Peak Systems utilizes a Software Development Life Cycle with the following phases:

Concept approval
Requirements analysis
Creation of specification
Development work
Peer testing
Project Manager testing
User acceptance testing
Release

We have multiple servers that we use for these different phases. We have a development server that we use during development and internal testing, we have a staging environment for user acceptance testing and finally we have a production server that we use after launch.

Peak uses Subversion (SVN) for source control and employs an internally developed Quality Assurance application for locating and resolving bugs during testing.

Peak embraces the Lean Software Development methodology for the efficiency and responsiveness that it provides. We also practice some elements of the Agile Software Development methodology. At the end of the day, Peak is pragmatic, not dogmatic. If something makes us more efficient, we embrace it.

Usability & Information Architecture

As the World Wide Web enters its second decade, we rarely encounter the novice user anymore. Each site that is created can build on the experience that each user has amassed. Users have certain expectations about where to find page elements like global navigation, search capabilities, contact information, and content. By utilizing, rather than fighting these standards, and taking advantage of what users already know, we can make the path to a successful website as short as possible.

Discovery

One of the most important components of Peak Systems’ methodology is our practice of performing a thorough discovery effort. We believe strongly in the value of a thorough discovery engagement to clearly expose needs and expectations prior to beginning work. Without exception, development engagements preceded by discovery have a higher rate of success and client satisfaction.