According to Greek myth, Cassandra's curse was that she could predict the future but no one would believe her prophecies. Sometimes the same can be said for project proposals. You can give the best assessment possible, but that doesn't mean the client will heed your words. Read on for encouragement.
It is difficult to exclusively use Scrum or kanban in product development, given the advantages they both provide. The prospect of using the two together can be just as difficult to fathom, yet it is possible for them to coexist—and with optimal results. Read on to learn how to combine the two.
A tool architecture is simply a picture of all your development, testing, and deployment tools and how they fit together. Creating a "current state" diagram and then looking forward and creating a "future state" diagram helps you understand where tool integrations would be beneficial.
Standup meetings are great in many instances. But if you're calling serial status meetings, you may find that people will stop attending. To engage employees and address issues quicker, you may want to try lean coffee or a problem-solving meeting. Read on for tips on involving your team.
In our latest issue of Better Software magazine, the feature articles focus on software licensing and ways to improve your team’s approach to process improvement. Creating software for a wide range of platforms is difficult enough, but enforcing software licensing also can be challenging.
Your managers want you to estimate features or projects months or even years in advance. But the work changes—or the code changes, or the people on the project change. What you thought might be a reasonable estimate four weeks ago looks wacko when you revisit it in six months. What can you do?
If the project you're managing goes better than planned—you finish ahead of schedule, under budget, or with greater results than expected—you might be inclined to chalk it up to luck and not want to draw attention. But here's an argument for why you should make sure people notice and you get credit.
Project teams have to learn to manage the difficult personalities they encounter on a project. The key is to identify which type of personality you are dealing with, then quickly apply approaches to smooth over the situation. Here are some tips for handling passive aggressive stakeholders' concerns.
Having participated in a number of unsuccessful metrics programs throughout his career, Lee Copeland has identified and distilled four key principles that help prevent the mismeasurement of software. Evaluate how your metrics work against these four principles. Do you need to make any changes?
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.