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. |
|
 |
Software Teams Aren’t Taking Bug Reporting Seriously Enough Of the things that are being sacrificed for speed, proper bug reporting is high on the list. Because it’s so easy to quickly update applications on the fly and push out fixes within days or even hours rather than weeks or months, plenty of teams assume it’s OK to ship something with a high volume of bugs. |
|
 |
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. |
|
 |
Preventing Workplace Miscommunication When one person says something that the other one misinterprets—a very common type of workplace miscommunication—the conversation often moves on with neither party realizing what happened. Being able to discover a misinterpretation and straighten it out before it escalates into a serious tangle is an important skill. |
|
 |
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? |
|
 |
Agile and Testing Change Can Come from Leaders at the Bottom, Not the Top Change doesn’t need to be a decree from the top that forces everything else to follow suit. Change can and should start from the bottom, and that happens after you empower your developers and testers and clearly show why things like agile are critical to overall success. |
|
 |
The Relationship between Agile and DevOps Many are touting DevOps as something new and different—just like agile before it. DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto. So why is DevOps viewed as something different from agile? |
|
 |
Understanding the True Meaning of Quality Day-to-day testing techniques, strategy, approach, and automation are all things that teams understand and will continue to implement, but how many teams understand the elements of purpose, belonging, transcendence, and storytelling as they apply to software quality? |
