Summary:

Typical client home page

• kinodb was used to develop a work management application for datb.
• The application is used to manage the workloads of the kinodb development team and kinodb consultants who are developing applications for clients.
• Clients can log onto Tracker and record bugs and enhancements.
• Progress can be track through development, testing, sign off and so on.
• Automatic emails are sent to alert users of any change which might effect them, e.g. to inform a user that an ehancement that they requested has now been implemented.
• The application enables clients to download the latest version of kinodb and view change history.
• Tracker also manages meetings and provides reminders of annual events such as birthdays and anniversaries.

Business background:

Internal user's home page

datb required an application which could be used both internally to manage individual work loads and externally to support client projects.

• The application needed to be accessible over the web using a browser with no additional plug-ins.
• The application required tight security to ensure that each client was only able to access their own data and be unaware of the activities of any other client.
• The client needed to be able to access their various kinodb projects; track progress, record bugs and enhancements associated with the project and allocate who was responsible for resolution.
• Bugs and enhancements needed to be tracked through to resolution and release.
• The latest versions of the core kinodb products needed to be available for download from the site, along with reports which detailed the changes included in each release.
• Each internal and external user of tracker needed to be able to access the list of items which were allocated to them and record their work as they progressed through their priorities.

Challenge:

A different internal user's home page

• Develop a robust solution which would be easy to use with no training.
• Provide clients with access to key data whilst ensuring a strict security model.
• Enable the management of kinodb projects, with geographically dispersed teams.
• Enable the client users to record feedback, bugs and enhancement requests.
• Make the application flexible enough to support each user's complete range of tasks.

Solution:

Project home page

• The initial solution went live after just a week of development, enabling early benefits to be realised.
• The application has evolved as users have identified additional requirements and changes.
• Regular incremental enhancements have been added to the project, expanding and modifying the behaviour as user requirements have evolved.
• The application is continually focused on delivering benefit and adapting with the business.

Techniques:

• Iterative development.  New features used internally first and then made available to clients as the application evolved.
• Actions are used to send emails on record creation and for change of status to alert other people on the progress and the potential need for action.
• Reports are used as a portal style interface, allowing immediate access to everything that the user might want to do.
• The reports only show relevant items for the specific user.
• Long lists are reduced to show only the top few items.
• Workflows are used to control the different items which required action, e.g. bugs, enhancements, etc.
• BLOBS (Binary Large Objects) are used to store releases and supporting material within the database, making it easy to exchange and share information between different users.