Skip to content

Comment on How to Run Agile Teams When a Team Consist of Smaller Sub Teams?parent

Comments

mjmjOP

Moral is fine, people are very engaged in their own project and turning out good work. Company is huge and projects have potential to make a large splash across divisions.

That's the conflict I have is: Do we all save time with more isolated and focused meetings at the cost of not know what the larger team is doing?

The overlap on current projects is non existent, but team members have occasionally partnered with other team members in the past (essentially swapping sub team members out) and there are rare occasions where someone complains about how they're blocked and one of the other sub teams has helpful advice or can pair with them.

Your last points about switching to Kanban and weekly updates is good advice, this is likely the correct answer.

So it's basically a bunch of startups within a company. Well, then I'd definitely switch to Kanban and have as little process as possible, just like Agile Manifesto says: Individuals and interactions over processes and tools

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.