Related Content
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. |
||
Seeking Feedback the Right Way Receiving negative feedback can be uncomfortable. You may immediately get defensive. But to grow personally and in your career, you need to be able to receive feedback—both good and bad. Here's how to recognize the three types of feedback you will get, and know how to solicit it and respond to it in the right way. |
||
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. |
||
Aging Gracefully in QA Employee churn is inevitable in every industry, and positions are being filled by fresh young faces all the time. Instead of becoming worried or insecure, senior team members should embrace their new status as someone to be looked up to for experience, lessons, and mentoring abilities. Here's how to do that in QA. |
||
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. |
||
Selecting the Right Agile Framework There are many frameworks available to organizations that are maturing their agile process. However, some frameworks can help reinforce agile behaviors, while others can actually drive an organization to revert to waterfall habits. The right choice should be the methodology that allows teams to deliver their best work. |
||
Quality Engineering in Agile and DevOps Ensuring that quality is advocated for at every step along the lifecycle can be tough. One easy response is, “Quality is everyone’s job”—after all, whole-team accountability is a key tenet of agile. But what does this really mean in practice? What approaches and roles help us embrace a culture of quality engineering? |