Related Content
Tips and Resources for Better Writing If you’re asked to contribute to your company’s e-newsletter or draft a blog post for the website or a design document, here are a few writing tips and resources you may find helpful. |
||
Improve Software Project Success by Conducting a Hudson’s Bay Start The Hudson’s Bay Company outfitted fur traders in the 1600s. To avoid problems when camping in freezing conditions, they'd send traders on a short trial expedition before the real one. This idea also can be used to reduce risks when starting a software project that’s complex, expensive, or disaster-prone. |
||
How to Release Anger at Work (without Getting Fired!) Have you ever felt so angry about something a colleague did that you wanted to punch the person—but you were still clearheaded enough to know that such a move would reverse the direction of your career path? There are better alternatives to clobbering a coworker. Read on for productive ways to simmer down. |
||
The Problem with Software Measurement and Metrics Many software practices rely on setting target numbers for the team to hit. But when a measure becomes a target, it ceases to be a good measure. People start gaming the system by changing their behavior in such a way to favorably adjust the measure in order to achieve the target. Don't get hung up on metrics. |
||
How Agile Bridges the Major Gaps between Development and Testing Agile, by its very nature, is about collaboration. The developers work alongside the testers, the testers see eye-to-eye (at least in most cases) with the developers, and there’s just a more flexible nature to the team itself. It is meant to bridge the major gaps within teams. |
||
What Not to Do if You Want Satisfied Customers You may think that overperforming would ingratiate you to your customers. But customers don't always want you to go above and beyond—often, they just want what they asked for. Don't fall for this common misconception. The trick to customer satisfaction is delivering just what they want—and good communication. |
||
Transparency Could Transform Your Company Transparency is a core Scrum value because it ensures everyone involved on a project has a common understanding of goals, progress, and deliverables. But what about extending transparency to the whole company, sharing revenue and client-related numbers, strategic product plans, and even individual salaries? |
||
Delivering Successful Software Requires You to Fail Faster The concept of failing has changed from something people dread to a necessary part of creating secure, functioning applications. That means that you don’t want to have one major failure at the very end of the development lifecycle—you need to continue to fail before release to find real success. |