Times of crisis can be extremely difficult. But crisis management does not have to be all bad. Dealing effectively with crisis can make us stronger and more successful. You can achieve success by recognizing the opportunity inherent in any serious incident. You just have to be open to change.
Ken Whitaker of Leading Software Maniacs gave the first keynote presentation at Agile Development Conference & Better Software Conference East 2014. It was titled “From Chaos to Order: Leading Software Teams Today” and covered his five tenets of leadership to restore order to product management.
Project and subproject boundaries can be challenging because people have different assumptions about exactly where the boundaries are. What, exactly, do your plan and budget include? Items on the boundary should be reviewed with project sponsors and documented as clearly in or out of project scope.
Schedules are tight, resources are scarce, customers are more demanding, the technology of today quickly becomes old news tomorrow, and competition is everywhere. We’re all doing much more with less. How do you improve yourself when under so much stress? This issue of Better Software has answers!
In some organizations, the project manager and business analyst roles are played by different people, and in others, one person performs both. The two roles require different skill sets, so it's important for both people to collaborate—or for the one person doing both to compartmentalize actions.
Where software development is concerned, good execution alone does not ensure a successful product. Even the best execution can’t overcome a terrible idea, a lack of shared expectations, or anything less than a total commitment to achieving excellence. Read on for tips to realize software success.
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.