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
This is a transcript of my keynote presentation for the Regional Scrum Gathering Tokyo conference on January 8th, 2025. They also love test-drivendevelopment, pairing, continuous integration, and evolutionary design. They tend to be passionate, senior developers. How are you measuring productivity?
Today, our ScrumMaster and their Team grapple with these issues, to help you understand how they affect a Scrum Team and what you can do to prevent them from dragging you down. It’s live, and books are selling and shipping. ScrumMaster Steve and his Team have released the World’s Smallest Online Bookstore. 3] [link]. [4] 4] [link].
Although this book is focused on individual Agile teams, many organizations have more than one development team, and they’re often dependent on each other to finish their work. Each coach will need resources, such as this book, to help them learn. Despite the name, it’s not a pure Scrum-based approach. Scaling Agility.
One of the recurring themes in this book is that, in order to be Agile, your organization has to buy in to the underlying Agile philosophy. With this book, the many free resources available online, and a dedication to learning, your teams can teach themselves everything they need to know. Investing in Agility.
There are two major ways to discover opportunities for cross-skilling: Kanban/Scrum Team Board. Kanban/Scrum Team Board. Skills Matrices and Scrum/Kanban Team Boards will only get you to the point where you know there is a need for growth, and where. TestDrivenDevelopment, Behaviour DrivenDevelopment).
The results will be more engaged team members, scrum masters, and a way of working that converts skeptics and naysayers into Agile evangelists. Engaged scrum masters are essential for long-term change (26:49). Scrum: Novice to Ninja: [link]. So, let’s take one of them, I think you said unit testing, is that right?
In many of them I see a familiar pattern: The managers and business analysts are sent on courses and sent to conferences and given books to read; most of them change their job title to things like Scrum Master or Product Owner; they create their plans using “stories” written on post-it notes, and they organise their projects into Sprints.
QSM found 11% defect reduction and 58% schedule reduction on a Scrum team; 75% defect reduction and 53% schedule reduction on an XP team; and 75% defect reduction and 30% schedule reduction in a multi-team analysis of thousands of developers. Test-DrivenDevelopment. Test-DrivenDevelopment.
Hi, I’m your Scrum Master,” she says. Most of these skills are out of the scope of this book. Until then, development on an Agile team looks similar to development on any other team. TestDrivenDevelopment. TestDrivenDevelopment. The next day, Claudine swoops in. “Hi,
Once you get past the sales pitches and confirmation biases, it doesn’t take much research to discover that agile and Scrum don’t have such a great track record. Question 1: Should you use Scrum or Continuous Delivery? Yet without a solid foundation in the technology that produces great systems, agile is pretty hollow.
The details of how to respond during an incident are out of the scope of this book. This practice, as with all practices in this book, is focused on team-level incidents—incidents which your team can analyze mainly on their own. Many of the ideas in this practice are inspired by books from the field of Human Factors and Systems Safety.
For this week’s Tuesday Lunch & Learn livestream , I have a special show for you: the new edition of my book, The Art of Agile Development, Second Edition. The Art of Agile Development came out in 2007. Book Excerpt. I’m going to be reading from the new edition of my book, The Art of Agile Development.
Lean is about Flow Efficiency The book This is Lean (Modig and Ahlström, 2013) describes “lean” as a relentless focus on efficiency – but not the kind of efficiency that cuts staff and money, nor the kind of efficiency that strives to keep every resource busy all of the time. 1990), which gave us the term “lean.”
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