Related Content
 |
Strategically Using Slack Time after a Release When you've worked for months on a big software release, afterward you may want to jump into the next project. But building in some slack time between sprints is a good idea. After a big release, there will probably be more work as new users discover bugs in your software. Plan for some more testing and development. |
|
 |
Achieve Repeatable Builds with Continuous Integration Continuous integration is essential to provide the feedback needed to keep a team’s code agile. One crucial aspect to a successful CI process is a repeatable build. There are two parts to maintaining a repeatable build: the idioms and practices to define it, and the feedback cycle to maintain it. Here's what you need. |
|
 |
Building Levels of Testing in Software Development Quality is now considered everyone's responsibility, and many developers are acquiring testing skills to validate their code before it gets to dedicated quality engineers. But where should you start? Consider beginning with unit tests that help you write better code, then building to integration tests and E2E testing. |
|
 |
8 Questions to Ask before Fixing a Defect Some defects require a fix, without a doubt. But not all defects are created equal, so careful thought should be applied before a defect is fixed. The goal isn’t to fix every reported defect; it’s to return value to the customer and profit to the company. These eight questions can help in the decision-making process. |
|
 |
Driving Agile Change: A Slack Takeover with Mary Poppendieck Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Writer, speaker, and author Mary Poppendieck hosted this Slack takeover and discussed all things agile, including how development has evolved over the decades and how to implement agile changes. |
|
 |
Figuring Out Your Regression Testing Strategy When your application is scheduled to go to production, the development team may be asked what their regression testing strategy is. This is a perfectly reasonable question, but a lot of people have a hard time answering it. Don't overcomplicate it. Analyze your process, look at the other testing, and put it together. |
|
 |
Reality-Driven Testing in Agile Projects Agile teams can drive down rework and devise more useful tests quicker by prioritizing reality-driven testing. This means tests based on reality, or relevant test activities above and beyond those derived from requirements. Learn some strategies to get real and design tests to locate important bugs that truly matter. |
|
 |
Is the Problem with Your Agile Tool, or How You’re Using It? While using index cards and a wall can function just fine as a kanban or Scrum board, issue-tracking tools such as Jira can make it easier to manage a backlog, especially with a distributed team. But these tools are more complex to use and can add their own overhead to the process. You need to keep things simple. |
