In after sales business well running service processes are among the most important prerequisites for meeting the demands of customers. As opposed to most tangible goods, for instance, services need to be newly implemented or adjusted to the customer’s requirements on a regular basis. Thus, constant improvement of processes is a permanent objective of Jetsam’s department for project management. Our team is built of highly qualified professionals, who bring in years of experience in service implementation and process innovation, including data analytics and reporting.
All change requests and suggestions arrive at the project office where they are transformed into service processes adjusted to the customer’s demand. This especially occurs whenever the customer’s product line is complemented or otherwise changed. Of course, the monitoring and analysis of processes in order to identify potential errors is also part of team’s daily business. In addition, they act as supervisor for Jetsam’s helpdesk by monitoring all ongoing activities and implementing improvements wherever necessary. In general, the project office is the coordinating center for projects which involve the customer as well as several departments at Jetsam.
Since all members of the team are highly experienced in their respective fields, they come up with solutions and improvement strategies that the customer often has not thought about in the first place. In short, they have learned to listen carefully to the customer’s needs.
The Jetsam project management team acts as the single point of contact for all change requests or ideas originated by our customers. Once a request is fielded the project team develops a project plan and works with you to transform your request into a changed or renewed process.
CLASSIC VS. AGILE APPROACH
The key to a successful projects starts with choosing the right project management method and tools. We hereby distinguish between the classic (waterfall) and agile (kanban) approach. But which methodology is the right for your product? In order to take this decision, the extent and requirements of each project will be checked. Weather everything can be fixed from the beginning, changes might be considered during the process or different releases are required, eather the classic or agile approach will be chosen. In some cases considering and combining both methods is also an option to receive fast and best possible results.
CLASSIC APPROACH (WATERFALL)
The waterfall model is a sequential (non-iterative) design process, each phase conception, initiation, analysis, design, construction, testing, maintenance of a product’s life cycle takes place in sequence, so that progress steadily flows downwards through these phases like a waterfall. Using this methodology you know exactly what to expect and have an idea of extend, costs and timeline of the project.
AGILE APPROACH (KANBAN)
In 50% of our projects more flexible methods are required in order to meet the customers needs. Even when things change the constant focus on value means what you’ve already delivered should be useful immediatley. An agile software development methodology is one which eschews a linear, sequential approach in favour of an incremental, iterative one.