[mattbrewsbytes]

We break work down into smaller tasks. We don't estimate anything and use Kanban boards to track work. Each column can be prioritized however the PM wants. Due dates are sometimes needed which just changes prioritization.

If there are cross-team dependencies we use feature flags or in cases where we're building something like a new API, agree on the API contract and ship it when ready even if the other team hasn't started. Follow-on items can be created and worked if we need to make changes or if bugs are found after the fact.

We use CI/CD with tests running on every deploy, this allows for deploying anytime and finding when dependencies are broken with new features.

[jamespaden]

Who breaks the work down: you or the PM?

Does the PM ever bother you to get the status of something, or is it always clear from the kanban board? I've seen the "bug the developer for a status update" move a lot in the past.

Agreeing on the API contract seems like a fantastic way to streamline the process!

[mattbrewsbytes]

The PM breaks down the work and we talk about new items as a team weekly, I (or devs) break down purely engineering work. The board is the status - its in progress, code review or getting tested. There are discussions on things as people work them - that's the small "a" agile practice of "individuals and interactions over processes and tools". Let those minor details get figured out as you work it rather than have everything planned, documented, etc.

[jamespaden]

Thanks for the insight!