This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Mike Cottmeyer was recently a guest on the Agile to Agility podcast with Miljan Bajic where he discussed Transformation, BusinessArchitecture, and Scaling. And I want to go to a topic, I haven’t discussed this with anybody on the podcast, I’ve done businessarchitecture. Listen now. Agile to Agility Website.
Whether you’re learning about businessarchitecture for the first time or dreaming of ways to grow your BA career into a businessarchitecture role, my conversation with Whynde Kuehn will help you discover the value of this role in an organization and what you can do to bridge that gap in your career.
Product Mismanagement. Most organizations fall in one of two buckets regarding their ProductManagement: Sales-driven, order-taking, and building whatever the customer wants without considering which projects will actually move the needle. Product owners building by directive. Inadequate Strategy Articulation.
I wasn’t actually trying to help anybody get better at software development per se, or productmanagement per se. And we’re looking for alignment between what I might say, like the businessarchitecture or the technology architecture and the organizational architecture.
We still need to have good architecture. We still need to have good business analysis and understand what’s really important to the market. Still needed, and more and more needed, super-effective productmanagement. And then from the businessarchitecture up, it’s more like a line to strategy.
What I had been doing was working with businessarchitecture capability models to try to come up with organizational patterns and work breakdown patterns that matched so we could get worked on organizations. And so we kind of had this key insight about the relationship between businessarchitecture and team design and enterprise agile.
And so if you show up and like you say, “Hey, I want to adopt Agile,” but you know, you’re not familiar with the strategies or Agile governance strategies or such, right? For example, teams may have the spirit of agility but be hampered by a poorly designed technical architecture that is not congruent with Agile principles.
And I was working for this VP that was like really super cool, is very into agile and we were coming up with really creative things for like team formation strategies and agile governance, all stuff. And businessarchitecture kind of a nebulous term, but how do you form teams? We have to figure out how to install governance.
Agile Release Train Roles and Responsibilities Each member of the ART plays a significant role: Customers/Users – Are the ultimate beneficiaries of the Product/Solution being developed by the agile teams. These are the individuals that are accountable for the outcomes and weigh in on important tradeoff decisions.
So we start with culture, maybe we go to practices and then all those teaming strategies and dependencies and governance and metrics and all that stuff that we struggle with all the time will just kind of work itself out. The Role of Governance Now, this is what I think about when I think about governance.
And if we can really take this first principle of encapsulation over orchestration, if we can take that idea all the way from the top of the organization all the way down and create these strategies across with minimal, lightweight, flow based governance empowered teams at the bottom right, then we’ve got a shot for. Great idea.
And what systems first means to me is that if we can get the teaming strategies, we can get the governance models, we get the measurement and control, we create the possibility for Agile to do really, really great things in your company. We want to manage those dependencies until we can break them. How do we govern for collaboration?
And what systems first means to me is that if we can get the teaming strategies, we can get the governance models, we get the measurement and control, we create the possibility for Agile to do really, really great things in your company. We want to manage those dependencies until we can break them. How do we govern for collaboration?
We organize all of the trending information in your field so you don't have to. Join 57,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content