Related Content
Aesop and Agile: A Moral for Effective Teamwork When a manager sees a problem on their team, they often want to act quickly to correct it. But if you take a “fix it” mentality too far, while you might get past the initial impediment, you have done little to help the team work better in the future. Let's look at another approach, based on one of Aesop's Fables. |
||
Achieve Success by Joining a Failing Project We all want to be associated with success, so when there’s a failing project, most of us want nothing to do with it. However, if you’re looking for a way to give your career a boost, you may want to rethink that. If you’re not afraid of a challenge, here are some ways embracing a failing project can help your career. |
||
The Good, the Practical, and the Expedient When a process isn't working, you'll have to make a choice that will help move things along. However, some choices are less about inspecting and adapting than about getting things done quickly, and that incurs risk. To manage this risk you need to be aware of the differences between "practical" and "expedient." |
||
Alleviate Employees’ Stress through One-on-Ones Simply having one-on-ones because they’re expected is not enough to realize their potential. To make one-on-ones effective, as the manager, you’ve got to be available, prepared, and engaged. It has to be more than a one-way status update. Here's how to use these meetings to promote trust, growth, and creativity. |
||
Merging New Codeless Test Automation with Your Existing Code-Based Test Scripts Adopting a codeless solution can be an amazing boost to quality, productivity, and tester career growth, but in most organizations, such test suites will have to be merged into existing code-based test scripts. To succeed, developers, testers, and management all should consider the differences between the two options. |
||
Making Decisions at the Right Level of the Organization Decision-making in a climate of ambiguous responsibility is a no-win situation. If you're in a position of some authority, how can you define exactly what that authority allows in order to better secure sponsor support for your decisions? It involves considering some scenarios and asking the right clarifying questions. |
||
Do’s and Don’ts for Having a Technical Lead on a Scrum Team Technical leads can be useful, both within the dev team and as a go-between. But is that a good idea on a Scrum team, which should be self-organizing? There is nothing wrong with having a technical lead on your team, as long as the role doesn’t impede the team. Here's where a tech lead can help or hurt a Scrum team. |
||
Beware the Bad Apple: 3 Types to Watch for on a Team We all know some obvious personality types that can be less than ideal to work with. However, there are other personality traits you may want to beware of as well. Although these characteristics may seem perfectly harmless on the surface, in excess they can be just as dangerous to a project as the more glaring types. |