Related Content
 |
Which Is More Important for Development—Software or Method? As project management software continues to gain popularity, which is more important—software or method? You rarely see a case study where a new tool or process didn’t have an immediate or fantastic effect, so how do you separate the signal from the noise and find the right solution for your team? |
|
 |
How to Make a Meaningful Apology Issuing apologies is often deemed a natural gesture, but how should apologies be made so that they are more meaningful? Good apologies thrive on honesty about the feelings, show genuine concern, and demonstrate fitting behavior. Anuj Magazine examines some recent public apologies that made the news. |
|
 |
Planning Techniques for Estimating Projects Agile teams often use estimation to plan projects. There are many different methods, and which you choose should depend on the type of work, what kind of deadline there is, and your team. Matt Heusser explains some estimating techniques that can expand your options when planning a work effort. |
|
 |
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? |
|
 |
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. |
|
 |
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. |
|
 |
Meetings: The Good, the Bad, and the Ugly Meetings are a crucial part of the communication process, but they endure a lot of ridicule. You can’t do away with them entirely—meetings are essential to an agile process like Scrum. Rather than avoiding all meetings, it’s better to work at making the times you meet with people more effective. |
