Riccardo Bernardini’s Post

A very interesting video about the state of current agile development environment. Something, which was called originally agile, has been changed to strict processes, excessive meetings, unmotivating work environment and failed planning and management practises. Perhaps we need to go back to well planned waterfall until we know how agile really should be implemented?

Those are provocative and delicate topics, but some that many companies with Agile projects struggle with. Ineffective and too numerous meetings and project managers that have no experience as a developer. So they lack street-cred and knowledge in a crucial are. And yes I have too often seen how they then try to rely on strict adhering to SCRUM or SAFe rules and focus on KPIs (Key Performance Indicators) to manage the team instead of giving them practical guidance and useful inputs for their daily work. What are your experiences with this? How did you handle such problems or even solve them? Please let's discuss this in the comments. #agile #projectmanagement #scrum #safe #development https://lnkd.in/giqcBYUz

Interesting video regarding the study of where many engineers pointed out that software projects adopting Agile practices are 268% more likely to fail than those that do not. Now as I have been interviewing, it has given me an inside look that it is very apparent that true agile is rarely practice and every place has their own version of what it means to be Agile. Could this account for the disparity instead of the blame on one actual methodology? Or maybe even companies choosing the wrong methodology for their teams. After all Agile was seen as a way to combat issues with Waterfall but again Waterfall methodology has been proven to work in the past and in some areas. So again, boils down to more in practice than actual methodologies in my opinion.

Signal-Boost-of-the-Day (SCRUM Edition): As a PRODUCT (not Project) Manager I don't really have a dog in the fight over methodologies. I've designed, helped build, and deployed products big, small, and in-between using Agile and Waterfall both. However... Based on my direct observations over the past ((mumble)) years, I think this video makes excellent points about the way that many organizations use Agile wrong. And hey... let's be honest: before those companies were 'Agile shops'. I'd bet they were 'Waterfall groups' with the exact same problems, mainly way too many meetings, too much stress from busy-body middle managers, and extreme anxiety over endless meetings and measurements striving to 'boost efficiency'. Not, you know, *using the end product as the measure* like is supposed to happen. Good PRODUCT Management is also critical to both Agile-built and Waterfall-built products. A good Product Manager will (as the video recommends) design an ENTIRE PRODUCT, with well-reasoned, financially viable, prioritized features, then break down those features' build-out into Sprints. Devs will be able to look at the big picture at all times. They'll see the target everyone is aiming for. Definitely worth taking a look - enjoy: https://lnkd.in/gsktvYWY

Navigating Software Development with Agile Methodology! Dive into the transformative world of Agile Methodology with my latest article. Discover how Agile fosters collaboration, adapts to change, and delivers high-quality software faster. 💡 Whether you're a developer, manager, or tech enthusiast, this read unlocks the secrets of Scrum, Kanban, and Extreme Programming. 🛠️ Let's innovate together! #Agile #SoftwareDevelopment #Innovation #TechTalks #opentowork #scrum

It’s time to move on from Agile Software Development (It's not working) My Experience: It is not the agile method that is the problem, but the challenge to use it in the right and effective way, without delusion. To know when and how to combine it with classic methods or use classic methods from the start, needs experience and open thinking related to the requirements of the project, especially of Multiprojects. You are welcome to watch also my Video in German, adressing the topic: Das Riesen IT Debakel - so wirklich geschehen! https://lnkd.in/eMVh4RzH Dee came across a study which found that software engineering projects have a 268% HIGHER failure rate when agile methods are used. And even though it might be biased, we can’t ignore the fact that there are some serious problems with Agile Software Development. You are welcome to get more information and experiences from my 39 years of experience by adressing me under: dirk.heuss@dhub.de You should do it in any case, if you are in the starting phase of a complex ICT Project with own and third party software development. Nobody would build a complex mechanism using only a powerful set of screwdrivers. Everyone understands that the toolbox should contain several tools and be appropriately equipped and professional for the task. There is no 'either or' here and a race in a complex project to see which of your own and external development partners is the best in terms of agile methods, casts a destructive fog, full of dark shadows, over the entire development chain. At the end - it does not work. Video-Timeline 00:00 Introduction 01:03 The real issue is not with agile itself 01:22 The amount of meetings 04:23 The Agile Project manager might be the problem 08:55 So what can software engineers do? Video-Source: Coding with Dee, 17.06.2024 https://lnkd.in/eANCrDb7

What is Agile Software Development? Agile software development is more than frameworks such as Scrum, Kanban, Extreme Programming, or Feature-Driven Development (FDD). Agile software development is more than practices such as pair programming, test-driven development, stand-ups, sprint planning, and sprints. Agile software development is an umbrella term for a set of frameworks and practices based on the values and principles expressed in the Manifesto for Agile Software Development and the 12 Principles behind it. #Agile #Scrum #Kanban #SoftwareEngineering

Waterfall done well is better than Agile done poorly

Because the first rule of agile is ‘be agile about agile’. I (with my team) tried loads of (new) tools and methods because everyone was talking about agile. In the end we realised we’d been doing our own form of agile all along, so went back to what worked for is. The biggest key things: - a simple whole team todo list that got archived (but still searchable) at end of each month. Some things got carried forwards. We had limited people. - a technical project manager role who anybody can message or phone whenever. - an emphasis of getting some part of a new feature in and live. Maybe within a few hours. And get feedback. - Chat to the users as often as possible.

Is Agile Project Management dying? Coding with Dee does a great job of describing what's wrong with Agile. My takeaway? Agile shouldn't be about more meetings, it should be about more effective communication. Agile shouldn't be about micromanagement, it should be about execution. For many companies and projects, a blended approach could be more appropriate than a dedicated agile project. A great PM will enable their teams to work while enabling all stakeholders to be appropriately informed. I love this video (bonus points for Def Leppard!) : https://lnkd.in/da6Wp8SD