Related Content
 |
When Buying New Software, Make Sure You're Getting What You Really Need The first step in any significant software procurement is to assure there is a clear definition of the business problem being solved. If you don’t know what you want, you aren’t prepared to negotiate for it, so you'll end up with a system or tool that isn't what you need—and you'll likely be disappointed at delivery. |
|
 |
The Key to Avoiding Procrastination If you have a task you've been putting off, dividing it into small chunks is a good idea. But the real key to overcoming procrastination is just getting started. Once you begin, you’ve built momentum and are likely to keep going, doing a little more until you’ve made good progress—and maybe even completed the job. |
|
 |
The Dangers of Underplanning in Your Agile Projects Agile coaches often stress the importance of not overplanning because work is later changed or never done at all. But consequently, many teams then fall victim to underplanning and aren't equipped for a successful project. Here are some planning activities that are critical to do before your sprints start. |
|
 |
How Do We Land This Thing? Planning for Go-Live and Beyond Some project managers have little experience bringing a project in for a landing, so they can be dismayed or just blindsided by organizational change needs and stakeholders’ expectations at delivery. Here is a checklist of some commonly forgotten items to address when a project goes live, so be sure to plan for them. |
|
 |
How Testers Can Collaborate with the ScrumMaster ScrumMasters serve the team by providing facilitation and coaching, but they also have many challenges. Those in testing roles are in a good position to collaborate with the ScrumMaster to improve agile processes. Here are some ways testers can partner with, support, and assist the ScrumMaster—and the rest of the team. |
|
 |
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |
|
 |
The Relationship between Agile and DevOps Many are touting DevOps as something new and different—just like agile before it. DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto. So why is DevOps viewed as something different from agile? |
|
 |
Balancing Process and Tools The limits of a tool may lead us to realize that we are not working as effectively as we can, and often, changing a tool is part of the solution. But there are good and bad ways to select a tool and how you use it. In particular there are risks when you focus first on tools before considering the problem. |
