Skip to Content

Is the end of Agile near?

Sogeti Labs
July 10, 2019

About the author

SogetiLabs gathers distinguished technology leaders from around the Sogeti world. It is an initiative explaining not how IT works, but what IT means for business.

Comments

8 thoughts on “Is the end of Agile near?

  1. Hi Edzo,
    While you make some excellent points, I do have an issue with you describing an agile team as having a product owner, a scrum master and team members. This is primarily Scrum and while Scrum is Agile, not all Agile is Scrum. Agile is a mindset, and while Scrum might not be the best approach for all companies, and might very well be a hype and at its end, an agile mindset and way of working will most likely always remain beneficial in any workplace.

    1. Hi Jessy, thank you for your feedback. And you are totally right. I link to the scrum definition, but i should change the wording “Primary an agile team” to “Primary an agile scrum team”. And also the point that you make that aspects of agile will remain beneficial is true, my question then would be “what defines an agile mindset”, and if it is about small incrementals and autonomy, then I think the reasoning still stands.

  2. Very good your article and I agree with the opinion of colleague Jessy (jully, 17)
    After all, what comes after the Agile? Will be the Modern Agile?
    What matters for the survival of an IT organization?
    Many IT companies have changed their story, survived and are evolving based on practice, and only improving agile practices in day-to-day deliveries.
    In my opinion, what comes next should be as good or even better than the great results already achieved with agile models.
    Let’s consider that many companies hide behind the concepts and do not solve their real problems and this nullifies any discussion about models comparison.

    1. Hi Thomas, I’m not in depth familiar with Nexus and Less. What is their approach to the business integration with the IT aspect of delivering value? My idea with SaFe is that it approaches IT still as IT only, delivering functions to the business organisation and not per see approaching Teams as Autonomous Business value teams. Do you know if Less and Nexus adres this differently?

      1. Not familiair with Less but about Nexus I have the following quotes from “The Definite Guide to scaling Scrum with Nexus : The Rules of the Game” that might answer your questions related to delivering value and being autonomous.
        “Refinement of Product Backlog items by the Nexus continues until the Product Backlog times are sufficiently independent to be worked in by a single Scrum Team without excessive conflict.”
        “Once the overall work for the Nexus is understood, Nexus Sprint planning continues with each Scrum Team performing their own separate Sprint Planning”
        “Product backlog items are deemed ‘Ready’ for the Nexus Sprint Planning meeting when the Scrum Teams can select items to be done with no or minimal dependencies with other Scrum teams”
        “The increment is ‘Done’ only when integrated, usable and potentially releasable by the Product Owner”

  3. Aw, this was an incredіbly gooɗ post. Taking the time and actual effort to make a good
    article… but wһat cаn I ѕay… I procrastinate a lоt and don’t manage tо
    get anything done.

Leave a Reply

Your email address will not be published. Required fields are marked *

Slide to submit