Related Content
During Times of Major Change, Keep People Informed During times of major change, readily available information can help reduce the fears of those affected about what it means for them. If you’re involved in implementing change, it’s wise to keep people informed—not just about the change itself, but also about its impact on processes, responsibilities, and expectations. |
||
The Manager’s Role on a Self-Organizing Agile Team Scrum and other agile methods focus on team roles and dynamics, and because of the emphasis on self-organizing teams, there’s sometimes a misconception that there’s no need for a manager. In reality, good people management can help an agile team thrive—the manager just has to know how to empower the team. |
||
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |
||
Balancing Process and Tools The limits of a tool may lead us to realize that we are not working as effectively as we can, and often, changing a tool is part of the solution. But there are good and bad ways to select a tool and how you use it. In particular there are risks when you focus first on tools before considering the problem. |
||
5 Myths and Misconceptions about Leadership It’s a common myth that leaders are born, not made. Even so-called natural leaders have plenty to learn about handling the kinds of challenges and problems they’ll have to face, and many others grow into the role. Let's explore this misconception and four others to learn that anyone with the drive can be a leader. |
||
Think through System Changes to Anticipate Quality Issues When you replace or significantly modify components of a larger system, too frequently we focus on whether the code we are building functions correctly. This is important, but it’s also short-sighted. It’s easy to introduce errors because we are changing interactions. Coding bugs are only one quality problem. |
||
Why You Should Have an Observer on Your Project Team If your project team suffers from misunderstandings or squabbles, it may be valuable to designate an observer role. This person would sit back and pay attention to whether there are patterns of miscommunication, interruptions, or conflicts that those in the conversations may not notice, helping resolve problems. |
||
5 Tips for Choosing Your First Agile Project When transitioning to agile, applying agile methods to a single project is a great way to get started. However, care must be taken to ensure the project you choose is appropriate—it shouldn't be too large, take too long, or be too risky. Here are five tips to help you pick the right project for your agile pilot. |