• Image de l'article
    Who we are
    Sept. 21, 2021

    Que sont-ils devenus?

    En déjà dix ans d'existence, Orphoz a vu grandir bon nombre de talents. Nous avons décidé d'aller à leur rencontre et de les interroger sur leur nouveau métier.
    Merci à Claire, ancienne consultante chez Orphoz, qui dévoile les coulisses de son rôle de PMO et consultante interne en industrie.

    Lire la suite
  • Image de l'article
    Who we are
    Juil. 7, 2021

    3 questions à Nam

    Découvrez nos talents et les différents rôles au sein du cabinet, à travers une série de portraits d'Orphoziens. Nam est consultante senior chez Orphoz. Avant de nous rejoindre, elle évoluait déjà dans le domaine du conseil et de l'entreprenariat

    Lire la suite
  • Image de l'article
    Who we are
    Juin 30, 2021

    3 questions à Alexis

    Nous sommes fiers de vous présenter les portraits de nos collaborateurs chez Orphoz. Cette semaine, découvrez celui d'Alexis, chef de projet spécialisé dans l’optimisation et la sécurisation de grandes transformations digitales, dans l’industrie et le secteur public

    Lire la suite
  • Image de l'article
    Abécédaire d'Orphoz
    Avr. 30, 2021

    S as Sustainable

     

    Lire la suite
  • Image de l'article
    Agile
    Déc. 18, 2020

    The video on Agile implementation pitfalls

    Implementing Agile can prove to be somewhat tricky. At Orphoz, we have investigated pitfalls to avoid on 3 key dimensions: people, process and technology. We have come up with pragmatic practices for you to try with your teams.

    Learn more with this 3-minute video and follow Bob, an IT project leader, on his journey to face Agile implementation challenges on each dimension.


     

    Lire la suite
  • Image de l'article
    Agile
    Déc. 16, 2020

    Conclusion on hands on guide to avoid pitfalls in executing an Agile project

    As you have seen through this series, there is no silver bullet for Agile project implementation success. The three dimensions – People, Process and Technology – are closely intertwined

    That is why our conviction is that you should go all-in and address all those issues simultaneously

    Lire la suite
  • Image de l'article
    Agile
    Déc. 10, 2020

    Technology - Pitfall#6: Being overwhelmed by technical debt

    You have been practicing Agile for a while now. You have improved how your team work together by setting the right management artifacts. But somehow, it seems that something is still wrong: 

    • The effort to develop new features grows continuously 

    • Releases cause regression in existing features 

    • Application’s availability drops due to unexpected bugs 

    These are common symptoms of Technical Debt

    Lire la suite
  • Image de l'article
    Agile
    Déc. 10, 2020

    Technology - Pitfall#7: Keeping old ways to test

    Fundamentally, Agile is about going quicker. Quicker interactions between Business and IT, quicker increments of your app in production, quicker feedback loops from customers. To achieve such velocity, every element of the product development lifecycle (Planning, Coding, Reviewing, Testing, Deploying and Operation) should be shortened. 

    Lire la suite
  • Image de l'article
    Agile
    Déc. 3, 2020

    Process - Pitfall#4: Underestimating planning value

    One of the most popular myths about Agile is that there is no planning and no structure whatsoever. Well you could not be more wrong. In fact, planning is key to define and structure your product roadmap and share it with your agile teams. Contrary to traditional methods where you plan everything in detail at the very beginning of your project, agile methods offer you a more flexible approach to maintain Agile main values: adaptability and commitment to the product vision. 

    Lire la suite
  • Image de l'article
    Agile
    Déc. 3, 2020

    Process - Pitfall #5: Not getting out of your Agile bubble

    In a non-Agile operating model, you have a complex network of day to day dependencies. Several types of dependency are inherent to non-Agile environments.
    In an Agile operating model, some of these team-level dependencies break away, but dependencies remain beyond the team level. It is important to set up enablers that promote coordination

    Lire la suite