How we work

Project start-up checklist

  1. Requirements get to know what the project is all about and what the client requires – and find all stakeholders, as some hide in corners!
  2. Scopeanalyse data to frame the project. This includes existing product metrics, customer feedback and market landscape. Find their current published examples, and ask them several times during the project, as examples are often found only as the project progresses!
  3. Define goalsthese must be clear, so that appropriate solutions can be designed to target them. Without it, it’s hard to defend a design. With it, we can explain how and why our design achieves the required goal. 
  4. Plan — a clear plan is drawn up before we start, setting out key milestones and what steps are needed to complete them.
  5. Affirm the vision of the project — a casual brainstorming session to ensure that the initial steps taken are going to be productive and misunderstandings are avoided.
  6. Estimate capabilities and capacities and establish a team.
  7. Keep it as simple as possible we don’t make the project more complicated than it is; we try to keep it simple using the most appropriate technology, appropriately.
  8. Plan for the unknownschedules change, people’s availability changes, things happen. We try to draw up realistic timetables that allow for contingencies so that we can guarantee deadlines.
  9. Re-use90% of our products include technology re-use at several levels. This saves time, reduces risk and embeds expertise.

During production

  1. Communication and listening to our clients. Get to know the client as well as  possible - understand their motivation and their goals and really listen to their responses. Ensure we incorporate what they have to say into our thinking rather than deciding everything in advance.
  2. Establish technical build workflow and communicate changes amongst the team on a regular basis.
  3. Keep the product specification up-to-date (use tracked changes and update the team with the changes, not the complete document).
  4. Monitor change requests and feature creep and feed back into overall plan.
  5. Regular progress checks against schedule and against specification and regular client signoffs at key stages - initially involving a wide set of key stakeholders, reducing this to a minimum (one or two).
  6. Technical standards check and Brand consistency checks.

Before release

  1. Validate product against specification.
  2. Test against standard test plan:
    • Accessibility checks
    • Multi browser checks
    • Unit tests
    • Quiz tests.

Realware products are compatible with Windows Vista
Welcome | Site Map | Contacts | RSS | Copyright 2007, Realware