Related Content
 |
Pandemic Challenge 205 of 7,923: Recognizing Project Milestones These days teams are compensating as best they can, but some aspects of project life are difficult with remote teams and social distancing. Celebrating milestone achievement is hard but necessary in our current circumstances. |
|
 |
Requirements Discipline: Avoiding “Death by a Thousand Paper Cuts" Absent an effective requirements baseline it is difficult to distinguish clarifications and error correction from enhancements and changes to the original ask. |
|
 |
A Tale of Toxic Sponsorship It is difficult to succeed without effective sponsorship—and almost impossible if your sponsor is toxic, as this true tale explains. |
|
 |
Schedule Risk Analysis Building schedules for complex projects is challenging. While the results are never perfect, credible schedules are a useful communication and coordination device. Incredible schedules are a dangerous waste of time and energy that damage a project manager’s credibility and cost an enterprise a fortune. |
|
 |
What’s the Problem with User Stories? Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile. |
|
 |
Comparing 4 Top Cross-Browser Testing Frameworks The market is flooded with cross-browser testing frameworks, with more options than ever before. How should you decide which option is best to test your application for compatibility with different web browsers? Let’s take a look at four of the top open source solutions today and compare their benefits and drawbacks. |
|
 |
5 Pitfalls to Avoid When Developing AI Tools Developing a tool that runs on artificial intelligence is mostly about training a machine with data. But you can’t just feed it information and expect AI to wave a magic wand and produce results. The type of data sets you use and how you use them to train the tool are important. Here are five pitfalls to be wary of. |
|
 |
Code Integration: When Moving Slowly Actually Has More Risk Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change. |
