Skip to content

Conversation

@LaurieCoq
Copy link

No description provided.

Copy link
Contributor

@lukewoodcock lukewoodcock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a nice overview. Who is this aimed at? Do you think it could be worth giving some substance to the practical workings of each strategy?

Like for example, what it is like / the effort involved in organising PI planning, indeed concretely what is a program increment or an agile release train.

And then for example with LeSS, how is overall sprint planning organised, when does it take place, who's involed, how it compares with organising PI planning. What does a single product backlog imply, who's responsible, can any team take tickets?

You can probably tell I have experience with SAFe but none with LeSS ^^. You've left me with more questions than before reading the article 😅

@LaurieCoq
Copy link
Author

@lukewoodcock This is an introductory article — the goal isn’t to present LeSS and its methods in detail, but rather to inform readers that there’s an alternative to SAFe and to spark their curiosity to learn more about it. I already have in-depth articles dedicated to each framework, but I don’t think it makes sense to merge everything into this one. I prefer writing shorter pieces and developing a series instead. My articles are already available in Confluence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants