Related Content
How to Succeed at Project Failure If you're bound and determined for your software project to fail, you're in luck: Naomi Karten has some advice for you. She'll tell you to set unclear objectives and unrealistic expectations, leave gaps in communication, and ensure a lack of resources and support. You'll be failing in no time! |
||
Who Is Responsible for Happiness? No one can take full responsibility for another person's happiness. However, a manager can create an environment in which a team can thrive, and that leads to happy environments. Being a servant leader means you don’t micromanage; you manage for outcomes. Is team happiness part of your culture? |
||
Evaluating Your Risks before Moving Data to Cloud Storage When companies move services to the cloud, security concerns don't disappear by transferring management to the cloud service provider. It's smart to familiarize yourself with what security controls the service provider has in place first, and to have ways of auditing those protocols as you proceed. |
||
How Technology Is Changing the Air Travel Experience Several developers are working on creating a personal flying experience for frequent travelers, helping them save time and fly hassle-free. These solutions charter private jets for their members, letting them bypass airport parking and security lines. What will it take to get them off the ground? |
||
The Google-fication of Uber We have Uber to thank for a new way to describe any job performed by part-time, temporary workers who are hired or dispatched via an app. There is an “Uber” for a wide array of jobs, and the list keeps growing. This story looks at some of them—and at whether this business model will keep growing. |
||
Focus on the Most Challenging Parts of Your Project We estimate to make decisions and to give an answer to the question, "When will this be done?" But estimation has limits, and trying to estimate too precisely in an agile project is wasteful. By driving the backlog based on priority, you can better deliver what is valuable to the business. |
||
Two Tales of Sloppy Service (and Their Very Different Outcomes) This story details two tales of sloppy service—but they have very different endings. In one case, the company representative refuses to acknowledge error or make up for inconvenience, but in the second, the rep apologizes and goes above and beyond to make it up. Which do you think retains customers? |
||
Meeting the Goal of Estimation The classic discussion for agile estimation is about whether points or hours are better. But there is now a third option: a movement called #NoEstimates. It actually does involve estimation, but you break down work in priority order and estimate only when you know enough to estimate accurately. |