Advantages and disadvantages of the Agile method on an S&H project
“An agile method is an iterative and incremental approach, which is conducted in a collaborative spirit with just the right amount of formalism. It generates a high quality product while taking into account the evolution of the customer’s needs” Veronique Messager Rota In the context of application maintenance for a major customer, Sqorus has signed a long term TMA (Third Party Application Maintenance) contract in progress since 2010.
HR Strategy
3 levels are represented within a team of 7 people, on 3 technologies (ETL: Datastage, Reporting: SAP BO, GUI: Peoplesoft)
Level 1: Direct support of the contact person for the resolution of minor problems. If not resolved: diagnosis and escalation to level 2
Level 2: More complex problems not solved at level 1 Resolution of problems according to the formalization procedure Formalization of technical procedures, modification of infrastructure (soft or hard) If not solved: diagnosis and escalation to level 3
Level 3: Specific support from the software publisher Very long waiting times
The TMA allows to provide a service called “dedicated” whose resources are exclusively dedicated to the customer.
The goal is to guarantee the maintenance of the application, its performance and its availability. In this perspective, the expected benefits of the Agile method are the following:
– Improve productivity through optimization with regular feedback
– Enable a reactive and iterative approach to work organization
– Focus on customer satisfaction quickly and efficiently
– Preserving investments
In 2 years of application of the Agile method, the results are very positive
– Subjects are constantly evolving and therefore the method is adapted
– Increased yield
– Better visibility of current topics
– Team cohesion: constant reflection to improve efficiency
– Valuation of people
– Decrease in anomalies over the months
The points of attention noted
– Requires a cohesive and motivated team
– Little room for substantive topics (The goal is not to have the same topic several weeks in a row)
– Difficulty to follow the life cycle of a development Pace of deployment Risk of collisions between subjects
– Support needed from sponsors
– Essential adaptation phase (continuous changes)
Before agile, the way teams worked was as follows:
– No or little knowledge of the subjects carried by each
– Few tickets solved in one week
– Lesser team sharing
With Agile, new practices have appeared
– Daily review every day Allows a good knowledge of each person’s situation Rely on each person’s skills
– Sprint review every week Plan the tickets of the week and distribute the tasks
– Sprint retrospective every week Review with the Product Owner the negative and positive points of the past week, and find areas for improvement
DOWNLOAD OUR LATEST WHITE PAPER FOR FREE
HOW TO MAKE THE MOST OF THE USE OF HRIS SOFTWARE IN YOUR COMPANY?
Also read in our file "Valuing the use of an HRIS software in your company":
- HRIS definition: what is an HR information system?
- Why implement an HRIS in your company?
- The different fields of application of an HR information system
- The HRIS: a tool at the heart of HR performance
- How to enhance your recruitment with an HRIS?
- Integration of new employees: how to optimize onboarding?
- Talent management: what does an HRIS tool actually do for you?
- The contribution of an HRIS in the management of employee training
- Compensation and payroll management: the benefits of HRISsoftware
- Absence management: HRIS software is there for you
- Social sourcing: ensuring communication between HRIS and social networks
- HRIS advantages: benefits for managers and employees