This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
That said, if I don’t summarize those labels, you will look elsewhere anyway, so here we go: Squad : effectively a Scrum team with a new name. EngineeringCulture that focuses on building Quality and Simplicity – build a Continuous Delivery pipeline that allows teams to deliver value independently of one another.
That said, if I don't summarize those labels, you will look elsewhere anyway, so here we go: Squad : effectively a Scrum team with a new name. EngineeringCulture that focuses on building Quality and Simplicity - build a Continuous Delivery pipeline that allows teams to deliver value independently of one another.
Of course, the reality is more complicated than this simplifying description, but you get the idea. Scrum [20] introduced iterations. But Scrum has failed to evolve fast enough. Dramatic advances in software engineering workflow can be traced to the 2010 book Continuous Delivery [22] by Jez Humble and David Farley.
This is a transcript of my keynote presentation for the Regional Scrum Gathering Tokyo conference on January 8th, 2025. It was September 2023, my CEO was asking me a question, and my position as Vice President of Engineering was less than three months old. Imagine were the best product engineering org in the world.
Of course, that’s always been the case. So, these are people I have run into over the course of meetups, online stuff, career, whatever. I mean we do Agile since she brought it up, but I don’t consider myself a scrum master or anything like that. Of course, there’s internal testing, but it’s short.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content