BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Presentations Microservices: Organizing Large Teams for Rapid Delivery

Microservices: Organizing Large Teams for Rapid Delivery

Bookmarks
32:33

Summary

Patricia Anderson, Micah Blalock and Jason Goth discuss the organizational structure and communication and development strategies and tools to allow teams to work in parallel without drowning in process overhead and coordination costs.

Bio

Patricia Anderson is an Senior Consultant with Credera with more than 6 years experience primarily in the Java arena. Micah Blalock is an Senior Architect with Credera with more than 25 years’ experience solving complex problems with software. Jason Goth is a Principal Architect in Credera’s Technical Architecture and Strategy Practice.

About the conference

SpringOne Platform brings together the people, process and tools for delivering and operating software services. Learn and share with the startups and enterprises leveraging modern Java with Spring connecting all the pieces of the modern software puzzle from developer, operator, architect, data scientist to executive.

Recorded at:

Jan 20, 2017

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • feels good reinventing the wheel in each company :)

    by Ionel Condor,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Many of these findings are actually pretty good documented and explained in agile frameworks like SAFe or Disciplined Delivery or in the Spotify model of scaling agile.
    The idea of multiple cross-functional teams, the scrum of scrums type of meeting with representatives, community of practice to make sure you learn together and apply the same standards on various layers.

    Every company is different I do admit this, but learning from others is in general the preferred way vs just learning everything from your own and saying "go read Mythical Man Month" ...really? if you knew it already why you did not apply those principles until it started to hurt ... proactivity and envisioning the future of the org was suppose to be a quality of the leaders. Sorry, I really do not want to be evil ...just wondering how come after so many years of agile software development we still repeat the same learnings: create cross functional teams, synch, agree on standards, trust people, etc ...

  • Re: feels good reinventing the wheel in each company :)

    by Daley Graham,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Because there are still so many companies around who haven't even learned this yet.

  • Re: feels good reinventing the wheel in each company :)

    by Jason Goth,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    The point is what you *think* is the right way to structure services, teams, standards, etc. when you start a project rarely is (right). No one has perfect foreknowledge. As you go through and add new capabilities, integrate with new customers, etc. you have to evolve the teams, standards, and so on as the product grows. In other words, you will *always* find new things that hurt. When you do, you have to go back to these principles and adjust - until something else starts hurting.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT