Do you hire a lot of external developers?

Onboarding vendors‘ developers

Large insurers, reinsurers and banks often have a lot of external developers from vendors joining their projects on a regular basis. Whether these developers come from the largest outsourcing companies around the world or small and very specialized consultancies, they often lack the knowledge of the bigger picture of the projects they join and, let’s be honest, feel a bit lost at the beginning…

One very experienced Agile coach working for a large bank told us very recently that he asked some third-party developers working for this bank (many of them based offshore): „Do you know who your client is?“, „Do you know what the strategy is?“, „What is the goal of our project?“, „Who are the decision makers and main stakeholders on the client’s side?“, „What are the KPIs for our success?“, „What are the key technologies involved besides the ones you work with?“.

The developers looked at each other puzzled. They had no clue.

We believe in empowering people rather than giving one order after the next. We believe that knowing your customer helps deliver a higher value.

This is the reason why creating online courses for onboarding at a TEAM’s level, including for externals – not only at company-level for employees – is key. It saves precious time – and money. However, so far it has been too cumbersome and expensive to create such online courses.

Thanks to our Course Wizard, this is now possible and faster than ever.

Do you have another experience, agree, disagree? Thanks for letting us know! We always appreciate feedback. 🙂

 

Read More

Agile, Lean, SCRUM?

If you have spent a bit of time with IT developers or project managers, you might have heard of „Agile“, „SCRUM“, „Lean“. These are key concepts and, in our experience, a must for any young and fast-growing company.

Here is an introduction that might interest you: https://www.mitchlacey.com/intro-to-agile/scrum/the-sprint-cycle

 

Here is also an overview of Agile software development principles:
(source: https://en.wikipedia.org/wiki/Agile_software_development)

The Manifesto for Agile Software Development is based on twelve principles:

  1. Customer satisfaction by early and continuous delivery of valuable software.
  2. Welcome changing requirements, even in late development.
  3. Deliver working software frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the primary measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly

 

Enjoy the reading!

 

 

Read More

Agility and Insurance: antonyms?

Insurance companies and agility

If you have found your way to this blog, it is quite probable that you work or have worked for an insurance or reinsurance company, or maybe a brokerage firm in this industry.

We see more and more projects popping up in the industry where companies claim to implement the „Agile“ methodology. According to your experience, is/was this company truly agile?

Join our discussion! (members only)

 

Read More
Senden