Which scenarios indicate that Developers are managing themselves well?

To determine whether Developers are managing themselves well, it's important to consider actions that demonstrate effective collaboration, ownership, and accountability within a Scrum Team. Daily collaboration to plan work is a key indicator of self-management because it shows that Developers are actively engaging with one another, discussing their tasks, and ensuring that everyone's efforts are aligned with the goals of the Sprint. This collaborative behavior helps the team effectively adapt to changing conditions and make informed decisions about their work priorities in real-time.

Creating their own Sprint Backlog is also an important aspect of self-management; however, it specifically refers to the initial prioritization and selection of tasks based on the Product Backlog. While this is critical, it doesn't capture ongoing collaborative efforts as comprehensively as daily planning activities do. Inviting management to Daily Scrums may indicate an attempt to involve others, but it might also suggest a dependence on management rather than showcasing Developers’ autonomy. Similarly, pulling tasks independently emphasizes individual action but doesn’t reflect the collaborative nature of Scrum, where teamwork and communication are paramount for success.