|
|
|
|
|
by Joeri
2968 days ago
|
|
There’s a fundamental divide that most of these tools struggle with which causes the sucky behavior: you plan work at the team level but you manage scope at the project level. If you don’t have a clear correspondence between teams and projects (a team owns a project and does all the work), it will be hard to manage in all of these tools, because you’re always missing out on half the story. The process packaging like scrum or kanban merely obfuscates the fact that the team/project mismatch creates the confusion. |
|