Related Content
 |
Building Good Scrum Habits Building good habits is an important part of an effective Scrum team. Habits are a form of automation: The more basic processes we can automate, the more we can focus our energy on hard things. The Scrum process, with its focus on rituals, helps us by providing a framework for collaboration and making it second nature. |
|
 |
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. |
|
 |
Before Data Analysis, You Need Data Preparation One of the prerequisites for any type of analytics in data science is data preparation. Raw data usually has several shortcomings in structure, format, and consistency, so first it has to be converted to a usable form. These are some types of data preparation you can conduct to make your data useful for analysis. |
|
 |
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. |
|
 |
Getting Support for the Tests You Need Done It’s often hard for teams to get sufficient time and resources for the amount and quality of tests they think are needed. It’s like management wants testing done but at the same time doesn’t want to commit what’s needed to do it. If that's your case, look at the business side, rank priorities, and negotiate resources. |
|
 |
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. |
|
 |
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. |
|
 |
Are You Forgetting a Stakeholder? Technology allows amazing innovations to optimize business and deliver new and better services, but if you don’t carefully consider your entire user community, innovations may cost you business. When designing for stakeholders, don't stop at the obvious cases—or else you may find that you forgot an important customer. |
