Do you think Agile sucks
Agile basically puts all the responsibility and blame on developers while letting product managers and owners just run the show and take credit . All they do is watch YouTube , go to a bunch of meetings and then breathe down your neck for a status . They don’t even explain the requirements well or understand it. Heck the developers have to come up with their own user stories . It gives everyone else the license to make mistakes and pivot except the developer.
In true Agile, the overall responsibility is on the PMs and POs.
How often do you see that happen ? I never see the blame for delays and issues be on poor requirements or management . It’s always the developer who did not work fast enough . In theory Agile is great , in reality it sucks.
@OP In my previous startup, we started following few rules when things got too messed up and management wanted too many things from us in a single sprint. We started having a rigorours sprint planning meeting where PM will explain each story to devs, QA, EM(entire team). We all have time to review and come up with questions the previous day. After that, we have estimation meeting the next day where we straight away rejected any stories which did not had proper clear cut requirements in written form(including any discussion we had on the planning meeting) and mocks. If any of this is missing, we won't give estimation and hence it will kicked out of the sprint. NO extra changes, addition of ANY sort will be entertained in the middle of the sprint. If you want, raise a ticket and prioritise it for the next sprint. If anything is too urgent, it will be included and a similar size ticket will be removed from the sprint. No type of stupid day-to-day request like "get me this data", "how does this feature works?" was entertained in the middle of the sprint either. All the credit goes to our awesome Scrum Master and EM who remained impartial to the team and PMs. I tell you what, the entire PM team completely panicked and went running around after 1 sprint. Their entire laziness was swept away and they went running around getting clear requirements and design on the day 1 of the sprint (because otherwise the requirement will be postponed to next). Seriously, they even complained that we are following very "strict" process. HAHAHA, they now know what we suffered. The "strictness" in process was eased out after a while from us but we are in so better position.
Somehow I can't deny OPs argument..lately I have seen Products managers are just talking and asking for stat updates.. something's not right ..
Agile is just a framework. Like anything in the corporate world, success or failure depends on adoption and execution. Company A’s philosophy will likely be different from Company B’s. For example, at some companies, other teams like Sales and Support can & do write some of the User Stories since they’re getting the direct feedback and scope from the prospect/existing customer.
I think agile is dead
Is there a different framework followed at FB?
Each team decides how to execute and operate
Agile is made for the f*** managers who just want to maximize on their engineers horsepower.
They sell it by saying "increased productivity of engineers", instead it actually is "increased pressure on engineers on daily basis"
But the newest cool job on the block is product managers .. I have seen lot of swe who got bored from coding jump to prod mgr where they are there just because they are technically more sound than a traditional PM. Dont know how that helps but...
Agile is good for managing remote teams you don’t fully trust. It’s also good to help management keep track of tasks and progress. The more process you impose, the slower and ahem, less agile your team will be. Introduce process in response to problems and with the team’s buy-in. Often some clown attends a 2-day Scrum Master training and thinks Agile is the solution to all the world’s problems, poverty, hunger, starvation, war. Ignore these people.
You people must have had some real terrible experiences to give you this much ptsd. Agile done right promotes empowerment, flow and trust using minimum necessary process and small batch sizes.
They sell Agile by saying "increased productivity of engineers", instead it actually is "increased pressure on engineers on daily basis"
Sooner than later, management would realize the same and if this is the scenario you described, it makes the job of PM and owners redundant