@crichardson@fosstodon.org avatar

crichardson

@crichardson@fosstodon.org

Learn-Build-Assess: http://eventuate.io, transactional microservices. http://microservices.io patterns. Author of Microservices Patterns. Frameworks. Consulting

This profile is from a federated server and may be incomplete. Browse more on the original instance.

crichardson, to random
@crichardson@fosstodon.org avatar

I'm excited to announce that I'm teaching a new public workshop starting in June: Architecting for fast, sustainable flow: enabling DevOps and Team Topologies thru architecture.

The intended audience are organizations that have adopted Team Topologies and DevOps (as defined by the DevOps Handbook).

In the workshop, I describe how to design an application architecture that enables the teams to deliver a fast flow of changes.

https://chrisrichardson.net/training-architecting-for-fast-flow.html

crichardson, to random
@crichardson@fosstodon.org avatar

A key goal of the microservice architecture is to accelerate development by simplifying the developer experience.

But you will only benefit from the microservice architecture if you design it correctly. And, use the right development process and organization structure.

If you don't, it will slow down development.

To learn more, please read this article:

https://microservices.io/post/architecture/2023/07/06/msa-is-meant-to-simplify-development.md.html

crichardson, to random
@crichardson@fosstodon.org avatar

Hey @TeamTopologies when I read this (pedantically) it sounds like:

"a stream-aligned team is a team aligned to a stream, which is aligned to a business domain/capability"

crichardson,
@crichardson@fosstodon.org avatar

@TeamTopologies

What is 'work'? Is it development work or business work?

And what does 'aligned to' mean?

And is there any relationship with that unspeakably-not-agile-process which distinguishes between operational value streams and development value streams?

Asking for a friend. 😀

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

Hmm.... what about the typical enterprise software development scenario?

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

Thanks for the clarification.

What about the definition of 'aligned to' which appears to have two meanings: (1) team aligned to a stream of work and (2) stream aligned to a domain?

Any comments?

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

And the team is aligned with the stream, right?

Team - <aligns to> - stream - <align to> - domain

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

Thanks. I will.

But just to be clear you appear to be saying that a stream-aligned team might not be aligned to a stream?!

Or do you mean to say that the stream (of work that the team is aligned with) is not aligned to a domain?

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

I'm feeling pedantic again and want to refine the definition of 'alignment'.

Previously, we discussed how a stream-of-work was aligned to a domain or fracture plane.

But the other part of alignment is the "team aligned to a stream of work".

One definition of "aligned" is that the team does the work.

What are the other definitions?

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

Sorry for not being clear.

I was asking about the meaning of 'is aligned to' in "Team <is aligned to> Stream of work"

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

Two other questions:

  • How many teams can be aligned to the same stream?
  • How many streams can be aligned to the same domain|fracture place|....?

I'm guess the answer to both is one, but ...

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

Hmm... I agree that a large stream of work with multiple teams might be necessary sometimes.

But wouldn't it be better to break up the thing-the-stream-is-aligned-to (e.g. domain) into loosely coupled subdomains.

Each of those subdomains has its own stream of work with its own team.

?

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies continuing the discussion earlier....

It seems that

'stream aligned team' = 'team aligned to a stream of work'

is really saying

'team does a stream of work' = 'team does work'

or perhaps 'team' - since team implies work 🙂

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

ie. The work part seems redundant

Team <is aligned to> Stream of work <is aligned to> Bounded Context | Fracture Plane | User Needs | User Journey | etc.

->

Team <is aligned to> Bounded Context | Fracture Plane | User Needs | User Journey | etc.

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

And in a software development context, <is aligned to> could be simplified to 'develops/delivers'.

Thoughts?

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

My goal is to find simpler (and more precise) words. 😀

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

That could be very useful.

However, I suspect the 'alignment' (a metaphor) is a tad fuzzy for most domains. 😀

crichardson,
@crichardson@fosstodon.org avatar

@matthewskelton @TeamTopologies

I meant the meaning of 'align' is a tad fuzzy.

But doesn't "aligning a team to a flow." rmean having the team do the work (of the flow)?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • Leos
  • tsrsr
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • hgfsjryuu7
  • Youngstown
  • InstantRegret
  • slotface
  • khanakhh
  • rosin
  • ngwrru68w68
  • kavyap
  • PowerRangers
  • tester
  • tacticalgear
  • cubers
  • everett
  • vwfavf
  • ethstaker
  • osvaldo12
  • Durango
  • mdbf
  • cisconetworking
  • modclub
  • GTA5RPClips
  • normalnudes
  • anitta
  • All magazines
    •