Related Content
 |
Measuring the Business Value in Agile Projects Venkatesh Krishnamurthy looks at some key ways to measure the business value of your project's agile performance. With consideration to the Agile Manifesto, Krishnamurthy uncovers different approaches to getting the most out of your user stories and defining true value. |
|
 |
A Tale of Two Projects Large IT projects are challenging. Complexity is hard to estimate well. Big systems are tough to implement. But when you're staring at a fast-approaching deadline and you know your system will not be functional in time to meet it, there are ways of handling the situation that are better than others. |
|
 |
How to Get People to Read Your Email Busy people—and even those who are not so busy—lack the patience to wade through endless emails, so you have to be clear, concise, and considerate if you want yours to be read. There are many ways you can communicate more easily and effectively, and Naomi Karten compiles some good ideas here. |
|
 |
AgileConnection Update: Transitions, Distributed Teams, and Managers Johanna Rothman, technical editor of AgileConnection, highlights some of the content that's being published on the site, including articles about using certain agile practices on an otherwise traditional project, the challenges of distributed teams, and another myth for misguided managers. |
|
 |
How to End Disputes Gracefully Given the many points of view in any work effort, disputes may be inevitable. The challenge is to gracefully terminate these disputes with none of the parties suffering black eyes or bruised egos. When you find yourself embroiled in a divisive difference of opinion, here are some things to try. |
|
 |
Understanding the Pace of Change: How to Stay Relevant in Your Role The rate at which we need to change and the speed of change are much greater than they used to be. We don't have as much time to get as deep in our skills, and we need to be more comfortable being generalists and picking up new skills, technologies, and processes quickly. Read on to stay relevant. |
|
 |
The Ambiguous Sounds of Silence: Why You Should Ask for Input Silence may not be golden when members of a team are trying to reach agreement, resolve an issue, or make a decision. In this setting, silence is often taken to mean that those who haven’t voiced an opinion approve of the matter under discussion—yet they may very well not. You should make sure. |
|
 |
I Don’t Sprint, I Stroll: A Non-Techie’s Journey to Product Ownership What happens when the director of marketing becomes a product owner for some of her company's web properties? She gets a crash course on the real meaning of agile development and her role in it all—and a newfound respect for the people who work in software engineering every day. |
