Related Content
 |
What’s a Tech Lead? Decoding This Developer Role The role of technical lead can be hard to define, and in many cases people accept the role without knowing its definition. Because new tech leads are used to programming, many focus too much on the technical aspects and not enough on the people and the team. Read on to learn what's required of this role. |
|
 |
Look to Corporate Standards to Guide Your Organization In large organizations with distributed teams, departments can have their own procedures, acting as if they are in completely isolated silos. One approach to solving this issue is establishing corporate standards. Tap the models of widely used standards to create practical guidance for your own organization. |
|
 |
How and When to Incorporate New Software Tools into Your Team Change isn’t always necessary—or even good, for that matter—but when is it actually the right time to incorporate a new tool, language, or piece of technology that might be taking the market by storm into your business? How do you identify the risks? |
|
 |
Drawing Motivation for Software Development Teams from Unlikely Places What do football or a submarine command have to do with agile success? At first, you might say, "Nothing." But football coaches, submarine captains, and their teams all have to establish a clear vision, analyze and prepare, and manage risks and adapt. Metaphors from other fields can motivate agile teams. |
|
 |
Use Process Improvement Methods to Elevate Your Test/QA Workflow Quality assurance testers may feel overwhelmed by all they have to do and the short time they have to do it. Implementing proven process improvement techniques can help streamline or replace existing models, making testers’ workloads manageable and letting them accomplish more—without sacrificing quality. |
|
 |
How to Deal with an Underperforming Employee (without Making It Awkward) Sometimes, an employee's ability just falls short of what your team needs. Talking to an employee about his performance can be uncomfortable, but it doesn't need to be. You need to make sure they know what’s expected of them, what kind of improvements you’re seeking, and how you’ll gauge their improvements. |
|
 |
Who’s Responsible for What? Use a RACI Matrix to Keep It Straight As projects get larger and more complex, roles and responsibilities can become confusing. To clarify, teams can create a RACI matrix: a chart that shows who is Responsible, Accountable, Consulted, and Informed for any work product. Each role has a different level of authority, so everyone knows their duty. |
|
 |
Agile outside Software: How All Teams Can Benefit Better collaboration, adaptive planning, early delivery, and constant improvement—do any of these agile pillars sound like something a non-software team would want to avoid? Agile has its place in different companies and teams across a multitude of industries. |
