Rumesh Wijetunge的动态

whoa! so many comments and some rotten tomatoes coming my way as well. Hey! My intention was just to stir up the pot a bit and bring out the importance of the human, the environment they are in, and their behaviors into the discussion. I do advocate Scrum or for that matter any Agile way of working to be practiced right, for the right context with a proper mindset. And yeah.. needed a bit of clicks.. objective achieved ??

Is this intentional to get attention and clicks? What you have described are organizational failures which have nothing to do with scrum. Scrum is a framework for rapid product development in uncertain area (VUCA). What is given is that the team is FOCUSED - which means they are assigned to a single _product_. Timeframes are there to establish predictability of delivery and business. You can release at any time, gather feedback at any time. Plan is on a cadence. Roles are actually quite well defined. If you don't know what the PO is doing then there's something utterly wrong in your product organization and the overall 'project' charter. Critique is always a great conversation starter, adding your counterproposals would make this more constructive. Agile and scrum are not about 'we can do whatever we can', there's a lot of discipline involved to get to actual outcomes. You can't really say "is it time to kill rice?" if you have never cooked it properly nor served it with anything worthwhile.

Rumesh Wijetunge As I’ve worked closely with you on integrating Agile at XigeniX, I’m compelled to share my perspective. Indeed, Agile possesses intrinsic merits, but its success hinges on the synergy of the right people, projects, and circumstances. Scrum is not a panacea; it demands individuals who embody the Agile mindset and values. Without this alignment, the expected outcomes of Scrum often fall short. We’ve observed this at XigeniX, especially with shared resources like UI/UX developers juggling multiple projects—a common industry challenge. Scrum can be less effective in such scenarios. Our experience further suggests that Scrum’s suitability varies across different stages of product development. We’ve found it less effective in early stages, leading us to explore alternatives during those phases. Recently, for more dynamic tech projects, we’ve started experimenting with Agile Extreme Programming Practices, finding Scrum’s pace and structure sometimes too slow and bureaucratic for our needs. Your call for a critical reassessment of Agile approach, particularly Scrum, resonates with our experiences in some projects. It highlights the need for adaptability in our methodologies to best suit our diverse project dynamics

Your whole argument hinges on companies who overwork their people. There is little value in spreading people so thin. Having a direct 1 to 1 relationship with your focused product would be much more efficient, and you would execute much faster. I’m not against whatever you’re arguing against scrum, but you can replace it with anything and you change nothing. Simplify to solve: PO SM scrum team member, that’s it, that’s the roles. Trim the excess. 1 product, 1 focus. However many teams, but 1, not 2/3/4. The arguments you had fall off

Rumesh Wijetunge How do you propose addressing the issues raised, such as too many ceremonies, inflexible time frames, and unclear role definitions?

You have team members serving in multiple projects and expect Scrum to work. I don’t need to go past that. Please do us all a favor and stop Agile coaching. Jeez.

Your 3 ?? are perfect examples of describing bad practices without understanding the true purpose behind Scrum.

The scrum framework is fine. It’s people and organizations who implement a version of it that forces too many rules and processes. The ememy of scrum is scrum done poorly.

Scrum is actually killing itself with every new guide version released. And this is a good thing. In the last one, they removed the line about "Their inspection should not be so frequent that?inspection gets in the way of the work". It was kind of the main idea behind having sprints and events cadence.

No, it's not losing it's relevance today. It lost it long, long ago already.