Is the chapter model working? I know this forum brings out the trolls. There are also some management folks who are definitely in the know giving us the real scoop at times. Can someone with some authority tell us that the chapter model works and here is what it has improved? Wouldnt the current sub chapter heads and chapter heads moving into actual delivery roles improve delivery?
14 replies (most recent on top)
I like the chapter model in that you can allocate resources easily and bypass the PDC, so it’s intended to be nimble and work sorta like contract workers, go where we’re needed, however where it fails miserably is domain knowledge and specific business competency and then you they’re trying to standardize everything by pounding a square peg into a round hole managed by people just as clueless. As for Agile, the Agile chapter manager CS who reports to the GM of Data Engineering, I’ve worked and known him for a bit and he’s the definition of an a.. kisser and brown noser if I ever met one, that guy will only talk to people who can get him places. The upper mangers I’ve engaged with and worth their salt is cyber guy CL, data performance MA , the chapter manager DP/SF, the rest are ok, but the absolute trash heap is ITFP RS, Data Engineering AG, CDO MC and HR managers.
@ljpy another thing in addition to agile is that most of the product owners don't actually know how to be product owners. they don't represent the real customers or end users from what i've seen. product owners are nothing but the tradition team leads and supervisors who tell people what to do even though they have no idea how to even define their product and/or actually run a project correctly because they're usually partnered up with a scrum master who is just as incompetent.
It would work better if Agile was not a chapter. When high level leaders figure out that it's all smoke and mirrors led by brown nosing useless people, we will be in a better place.
It’s working well in the sense that all the up skilling, training, certifications, new job titles, and Digital / Agile jargon fluency are helping people land at Amazon, Microsoft, Salesforce, etc
Is it working?
Has it actually increased oil production or decreased drilling and completions costs?
And I’m not referring to the ‘non-gaap’ type accounting we did back in the day when the lean sigma folks were all trying to justify their positions.
Every day, I do three things:
Leverage agile frameworks
to provide a robust synopsis
for high level overviews.
Create iterative approaches to strategy to foster collaborative thinking and further the overall value proposition of Chevron.
Organically grow the holistic world view of disruptive innovation via workplace diversity and empowerment.
You’re welcome.
:p
The new Chevron structure is nothing but acronyms and trendy names for the same old organization. Things are actually going backwards while everyone tries to figure out all the new buzzwords, and who is actually in charge.
I personally like my chapter manager, but the chapter structure is strangely disconnected from epic and BU goals. If the idea is that individuals should be assigned to specific stories for a sprint, then it is the feature or epic managers who should assess your contribution (and EOY ranking). If that, then what does a chapter manager contribute beyond redundant meeting attendance.
There's definitely a gap of product managers avoiding responsibility like the plague. They are so afraid of being accountable for decisions, but they get paid the dough because they are supposed to be. I.e. they get paid for not doing their own job. What leadership...
i like the epic owners being responsible.... too bad the product line managers we have in place avoid responsibility like the plague. PO's are now epic owners too (on top of features, on top of story acceptance). Push the decision to the product owner yes, but damn... at least understand what is in the epic and what you are driving towards because when you reprioritize its on you not the team. Learn how to use ADO and not a dashboard some consultant whipped up that is always green.
Some chapters are ok. Others are not.
Another new program?! Haha.
The should get rid of chapters all together and just have epic managers directly above feature owners. Too many managers with overlapping scope just gridlocks the system.
delfi deployment has been a complete f-up with the blind leading the one eyed. Is that any reflection on how well the new chapter model is working?