The WorldPartner Toolbox

Description

Scrum

This methodology helps manage the processes related to the development of complex software. It includes various practices in planning, estimations, delivery, sign-off, fixed meeting dates, and reviews.

Newsletter

This is a weekly report sent to all stakeholders that informs them of the activities that have taken place as well as clarifies unresolved tasks and issues. It further presents a number of KPIs that ensure transparency as to the performance of the team as well as its individual members.

Build strategy

This is the set-up of a nightly build server environment which includes the running of automated tests. The automated reports to the team tell them what tests failed and if there are any problems during the build.

Technical strategy

This is extremely important, even when the team is continuously building on an existing system. It defines the componentization of the code, keeps the code easily understandable, comments on the code, undertakes ongoing refactoring needs, and manages technical debts, logical interfaces, assumed future extension needs, structural opportunities versus product long term viability, and much more.

Functional standard guidelines

WorldPartner proposes that teams sign up for as many elements of the WorldPartner Design and QA Bible as possible. This includes hundreds of best practices to guide the specification of designs in terms of usability, look and feel, localization and internationalization, validations, user experience, performance and much more. Signing up for any of these best practices means that designers and testers will have to ensure consistent compliance for both existing and new codes.

Documentation standards

This refers to specification standards for functional and technical designs (generally WorldPartner adheres to UML 2.0), help files, and supporting documentation.

Coding standards

Generally this requires strict compliance with WorldPartner’s existing coding guidelines. For .Net based projects, this includes the set-up and adherence to rules defined in FXCop (static code analysis tool), including but not limited to:

• Correctness;
• Library design;
• Internationalization and localization;
• Naming conventions;
• Performance, and
• Security.

Code sharing practices

This refers to the set-up of a code sharing system and strategy -- when to commit, comments to apply to commits, merge standards and responsibilities, etc.

Testing environment

Setting up standards for testing in regard to Unit Tests, Automated Tests, and Test Cases comprise the testing environment. This includes testing plans in terms of supported environments (operating systems using VMWare setup) and browser support needs. It also takes on the specification of requirements for security testing, functional testing, compatibility testing, load testing, performance testing, regression testing, and usability testing.

Bug, task and feature tracking

This includes setting up a system for tracking bugs, features, and feature requests and tasks. WorldPartner is currently using Ontime from Axosoft for most clients, but depending on client needs, a different tool may be proposed.

HR development strategy

Members of a new ODC are not expected to know all technologies and methodologies from day one. Software technology is evolving at a tremendous speed and the only way to keep ahead is to make sure that one’s employees are up to date with the opportunities that technology offers. WorldPartner has a shared interest in keeping manpower informed and capable of using the newest development technologies and methods; thus, it offers all ODCs and their team members free training. Subjects typically relate to improving design skills (e.g. UML) and understanding newer development methods (e.g. jQuery). ODC clients can request training in areas they feel will benefit the team.

Knowledge base

This refers to setting up knowledge sharing structures including access to a team Sharepoint site and a wiki with best practices.

Management methodology and review structures

WorldPartner adheres to the One Minute Manager approach (Blanchard and Johnson) by using an individual employee goal-setting template and continuously monitoring the person’s fulfillment of these goals. This is combined with personal and team KPIs to make it possible for each individual to see how he can improve performance and thereafter, progress in his career.