Rabbit Stoddard, Mo Jave maybe have insight. Implementing scrum or something like it. It is likely we'll have this discussion with the cruise end of the business next week.
This group has always provided analytical services for the company at large. With the departure of
Starting next week, we are moving to a 2-week release cycle for each of our major components. Each client -- briefly, air, hotel, and cruise -- will have a specific primary point of contact who is responsible for prioritizing work. We'll have standing every two week meetings to show what we've done.
Our goal is to automate our current work, freeing us up to do higher value work -- and then automate that. The center piece of this for each client is the business data architect. Ad Hoc work and work we haven't yet automated rests wth the architect. I'll act as lead architect, and the champion of this methodology.
Doing the automation are our DBAs. The business data architect will help the DBAs understand the business and develop products that solve problems for our clients. The DBAs will be in South America, and their work will be directed by the product owner and Architect.
This is where we're starting. If we need to make changes, we will. If we need to put more resources towards a specific client or product area, we will.
Mostly. It has a lot of jargon in it though. You might want to simplify. Especially if you are aiming to change behavior.
ReplyDeleteProduct Owner, Architect, and DBA? Yeah, that's a little jargony.
ReplyDeleteBacklog? Yeah, same thing.
I'll work on that.Thanks.
Ni... I meant there's a lot of buzzy business speak catchwords:saddle point, pivoting, champion, etc..
ReplyDeleteWho is your audience?
The business units. VPs and crap.
ReplyDeleteI don't want to say "Because X and Y are leaving, we're free of some weight and can do more better things", as it sounds like I'm tossing those people under the bus.
ReplyDeleteI wouldn’t even mention them, unless someone asks why you didn’t implement this idea earlier.
ReplyDeleteWho is protecting the DBA’s time, and managing their day to day progress? What about work interruptions on new development, either new bugs or existing technical debt/issues?
.sub
ReplyDeleteRabbit Stoddard Protecting of the DBAs time is some amalgamation of the PO and the architects. In reality, the folks going into the architect position have been doing a lot of crap that we need to automate, so they'll help the DBAs do that.
ReplyDeleteAs for existing technical debt, we're a little bit declaring bankrupcy. There's a lot of things this time is relied on to do, and they've never been done systematically.