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
I've been writing about agile softwaredevelopment for nearly 20 years, and most of it is available on this blog. Testing Without Mocks: A Pattern Language - 27 Apr, 2018. How to use test-drivendevelopment without traditional test doubles. Test-drivendevelopment in a nutshell.
I've been writing about agile softwaredevelopment for nearly 20 years, and most of it is available on this blog. Testing Without Mocks: A Pattern Language - 27 Apr, 2018. How to use test-drivendevelopment without traditional test doubles. Test-drivendevelopment in a nutshell.
Most softwaredevelopment efforts have a hidden delay between when the team says “we’re done” and when the software is actually ready to release. One of the early adopters of continuous integration was ThoughtWorks, a softwaredevelopment outsourcing firm. Without exception, it must always build and pass its tests.
Each failure, no matter how minor, is a clue about the nature and weaknesses of that development system. 2010] and [Dekker 2014]. 2010] and [Dekker 2014]. Softwaredevelopment has different constraints, and some of those transplanted ideas may not apply perfectly. Failure is the result of many interacting events.
He led softwaredevelopment at Salesforce.com during its years of hyper growth, and is now SVP of Engineering at Twitter. One of the things Scrum has contributed to the practice of softwaredevelopment is the idea that small autonomous teams perform much better than large project teams or single-discipline teams that work in sequence.
Thus instead of copying lean manufacturing practices, lean product development practices must evolve from a deep understanding of fundamental lean principles adapted to a development environment. Lean SoftwareDevelopment: A Subset of Lean Product Development In 1975, computers were large, expensive, and rare.
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