Related Content
Tips for Getting an Agile Transformation Off the Ground Many agile transformations are doomed before they even begin. Organizations focus on the wrong things up front, resulting in a poorly planned effort that doesn’t deliver business value. Here are some tips to get things started the right way, including how to communicate well, define roles, and change your culture. |
||
A Software Testing Primer When development teams are pressed for time or budget, testing is often the first activity squeezed out. But testing will actually save you money in the long run. This story gives the basics of why it's crucial to test early and often, the types of testing you should perform, and how to get proactive against bugs. |
||
Testers Must Use Team Connections to Enable Quality The quality team has the greatest reach in its visibility and ability to connect with all other engineering and non-engineering teams. For a tester to realize their fullest potential, they need to acknowledge and leverage this reach by communicating and collaborating with all other teams to create the best product. |
||
Security Testing and Assessing Risk: A Slack Takeover with Shachar Schiff Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Shachar Schiff, founder and principal consultant at BadTesting, hosted this Slack takeover and discussed assessing code coverage like a risk analyst, risk assessments outside security, and more. |
||
2 Ways to Standardize QA Practices Testing can get complicated when each project is using a completely different toolset, language, and reporting status, with different measurements and formats. Testing is a reaction to context and what we encounter, so how we test cannot be standardized. What we can standardize is the stuff that surrounds the testing. |
||
Rethinking Your Measurement and Metrics for Agile and DevOps In their transition to agile and DevOps, many teams forget they also need to update their measurement and metrics plan. Some measurements and metrics from the traditional waterfall software development lifecycle may remain useful, but many may not provide value—and some may even adversely impact progress toward goals. |
||
Supporting Scrum: Adopt before You Adapt Scrum is a fairly minimal agile process framework that you can adapt to work best for your team. But adaptation works best once the team has internalized the principles and values of the Scrum process, and that takes practice. In other words: Before you start to adapt Scrum, first try fully adopting the framework. |
||
Understanding the ScrumMaster's Role in Team Communication Some agile teams believe the ScrumMaster is the sole point of communication between them and the product owner, so the team can abdicate any responsibility to communicate with stakeholders. That couldn't be more wrong. It's actually the ScrumMaster's job to enable communication and coach or guide the team to solutions. |