Want further evidence that Continuous Testing has evolved from buzzword to business imperative? New Forrester research found that Continuous Testing, done properly, is a key differentiator between DevOps + Agile leaders and DevOps + Agile laggards. Here are the key findings and recommendations from that research project. Key Continuous Testing Findings 1. Five Core Continuous Testing Practices Sep
A lot of articles address the role of tech leads and engineering managers. One common theme we often come across is how to increase a team’s productivity. But before you focus your energy trying to increase their productivity, you might first want to consider what’s destroying it, to have a sound base on which you can build. Unfortunately, even though Peopleware was published almost 30 years ago,
According to the Scrum Guide, Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. But Scrum doesn't prescribe how you do it, and for good reason. Refinement is an ongoing process. It never stops because requirements and opportunities never stop changing. Detailing everything up front would create waste and also delay the delivery of value.
To gather insights for the current and future state of automated testing, we asked 31 executives from 27 companies, "What are the most significant changes to automated testing in the past year?" Here's what they told us: Adoption Evolution plus shift in recognition that testing is strategic to the company’s mission. As important to the success of the software as the software itself. Shift left – e
To gather insights for the current and future state of automated testing, we asked 31 executives from 27 companies, "What are some real-world problems being solved by automated testing?" Here's what they told us: Benefits Simply put, automated testing is invaluable for 1) Saving time - as tests are run automatically 24/7; 2) Reporting - we get daily insights; 3) Consistency and accuracy: manual te
Software development has changed. Long gone are the days of isolated dev teams and disorganized rollouts. Today, successful development teams are dedicated to operating rapidly-changing, resilient web systems at scale. With so much collaboration, organization is important for the safety and security of any system. Continuous integration and continuous deployment are central to keeping updates stea
The Sprint Goal is an important part of Scrum. It's like a burning torch that unites the Development Team and helps it move forward during the Sprint. However, the Sprint Goal is not discussed very often, and in this article, I would like to talk about the deep importance of this component. First, let's look in the Scrum Guide and see how it describes the Sprint Goal. The Sprint Goal is an objecti
The role of the Scrum Product Owner is probably the most misunderstood of the three Scrum Roles. As I look back at the different incarnations and interpretations I have seen of Product Ownership, I thought it was time to articulate the different stances I thought an effective and professional Scrum Product Owner might consider. Inspiration Besides my industry experience, my ideas were influenced b
Hi, everyone! In this article, I'd like to share my list of top 30 books for Scrum Masters. I've read all of these books and used them in my practice. They actually work! The books cover all eight areas of the Scrum Master competency model developed by the Agile Coaching Institute: Agile-Lean Practitioner This is the first and foremost area of a Scrum Master's skills. A Scrum Master is a practit
The Problem: Confusion, Uncertainty, and Delays We find this a common thread amongst our customer teams, which can be attributed to a lack of backlog refinement. A team is planning their next sprint. One of the developers looks anxious: “What do you mean we are changing the way we list items? This is going to be messy – does finance know? Well fine, we can do it, but it’s not on me when we have t
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く