|
Strategies for Implementing Agile in Small Organizations The experience of implementing agile in a company of thousands of employees differs widely from that of a company of hundreds. Although the risks can be greater, the rewards can be, too. If you work in a small company that is interested in transitioning to an agile workflow, consider these strategies for implementing agile in small organizations.
|
|
|
The Reason Scrum So Often Fails Agile Teams The core of the Scrum framework for managing product development is the three key roles: ScrumMaster, product owner, and the development team. This triad is what makes Scrum so successful—when it works. However, it is the absence of these three roles that is the root cause of the majority of unsuccessful adoptions.
|
|
|
The Mindset of the Agile Developer Most software development teams these days adopt an agile approach to guide projects through their lifecycle. But, according to Gil Broza, embracing popular practices is not enough. To work effectively in an agile environment, developers must change their mindset.
|
|
|
Can one person have the role of both product owner and scrum master and perform each role effectively? I'm currently in a situation where my organization wants to transition to using Scrum for software development and enhancements but we don't have a clear idea as to who will assume which role. Any feedback is appreciated. Thanks!
|
|
|
The Values Essential to a Scrum Software Development Practice The Scrum Guide was updated recently to make values an explicit part of the framework: commitment, courage, focus, openness, and respect. When these values are embodied and lived by the team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone. Is your team practicing them?
|
|
|
Don’t Make These Scrum Mistakes
Slideshow
Scrum is a project management framework and does not specify a set of how-tos or checklists that some other development processes define. Since Scrum can be implemented in various ways, it is easy—and often common—to misinterpret Scrum’s guidelines and make mistakes while implementing it.
|
Sumedha Ganjoo
|
|
Scaling Scrum with Scrum™ (SSwS): A Universal Framework
Slideshow
Scrum is a simple framework allowing a single team, working from a single backlog, to maximize the value it delivers to its stakeholders. Unfortunately, your organization probably has more than one team and more than one backlog—but you still need to maximize the value to your stakeholders.
|
Dan Rawsthorne
|
|
Code Factories: Making Agile Work in Large Organizational Teams Making the transition to agile can be difficult for teams that are used to working in large groups and reporting to a single manager. Kris Hatcher suggests a new way to work: in smaller teams called code factories, which are created to stick with a specific product throughout its lifetime.
|
|
|
Value Metrics for Agile Governance In agile projects, team-level metrics are not useful for planning and monitoring projects across a software development organization. According to Mike Harris, the best value measurement should be based on providing customer value.
|
|
|
Do Cross-Functional Teams Mean Cross-Functional People? Managers who want high-performing agile teams may think this involves finding people who all possess every required skill. But in addition to that being unlikely, it would also be a bad idea; it's the mix of perspectives that really gives benefit and value to the business. Instead, find experts in individual skills who can collaborate well together.
|
|