3 ms·
I can say I worked on one. But because it was well managed, small team, everyone listened to each other's areas of respective expertise and authority, we wra
by ACow_Adonis 7y ago
I can say I worked on one.
But because it was well managed, small team, everyone listened to each other's areas of respective expertise and authority, we wrapped it up in a year on a 6 digit budget.
Meanwhile, a previous project elsewhere i have experience with, had a team of approx 30 cycle through, 10 to 20 external consultants (some flown in and put up in hotels, but who had no actual experience in the things they were consulting on) , had been running for several years, estimated 8 digit budget, and by the time i left had been running for several years with no discernable output compared to the status quo except reports and presentations taking about how good things would be one day in the indeterminate future.
I'm convinced the later is the norm, and it's even harder to go back to once you've worked on a project that 'just works', but I'm sure several people used the later one to land themselves high paying jobs by putting it on their resume using management speak to make it sound impressive, so I guess success depends on whose point of view you're looking from...
- ethbro 7y agoFrom my experience in consulting and internal, there are two major things you can do. 1) Use objective KPIs + encourage a culture of admitting, taking responsibility for, and being forgiven for failure Failing to admit failure is incredibly toxic to ongoing corporate functioning, and a culture that doesn't allow for it endlessly moves goalposts until there is success (by some metric) without motion (by objective metrics). 2) Don't allow anyone to overscope sprints If all the "team" can accomplish is a "Hello World" in the next week, then that's the goal. Better to be honest than slide down the slippery slope of lying to ourselves.