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
Martin Fowler wrote an article in 2003 titled Cannot Measure Productivity. Kent Beck concluded , Measure developer productivity? We use Extreme Programming as our model of how to develop software. They also love test-drivendevelopment, pairing, continuous integration, and evolutionary design. Not possible.
Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Test-DrivenDevelopment. Test-drivendevelopment encourages you to think about and improve your design at nearly every step.
There are a ton of examples of how much software is around us: cooling systems, our cellphones, automatic doors, microphones, cars, traffic lights, etc. It is not something to be taken lightly, the future will be built by us developers and we sure want a good one, not one in which things from the past were easier to use. Refactor?-?Eliminate
Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Not just spending money—that’s comparatively easy—but making real, meaningful changes to organizational structures, systems, and behaviors.
So, what allows me to do this—what allows me to do this show, this software development show every week, and what allows me to write this book—is the people who hire me for training and consulting. First, business analysts would interview stakeholders and document the system requirements. In theory, anyway.).
Instead, Modig and Ahlström demonstrate that lean is about flow efficiency – that is, the efficiency with which a unit of work (a flow unit) moves through the system. In my case, the dental system was focused on the efficiency of the lab’s milling machine – no doubt an expensive piece of equipment. Consider our dental experience.
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