Richard Hundhausen
[email protected]
@rhundhausen
So, who designed this thing anyway?
BDUF
Waterfall
Emergent
Some
DUF
Cowboy
Q.
A.
Disambiguity
Behavior-Driven Development (BDD) Domain-Driven Design (DDD)
Liskov Substitution Principle (LSP)
Defensive Programming
Don’t Repeat Yourself (DRY)
Dependency Injection (DI)
Interface Segregation Principle (ISP) Separation of Concerns (SoC)
Dependency Inversion
Inversion of Control (IoC)
Single Responsibility
Design by Contract (DbC)
Principle of Least Privilege (PLP)
Test-Driven Development (TDD)
Open-Closed Principle (OCP)
And my favorite: YAGNI (You Ain’t Gonna Need It)
Refactoring Tools
Refactoring Support
Refactoring Support
Refactoring Support
http://bit.ly/egJdcx
1.
2.
3.
4.
Be Transparent
Resource: Professional Scrum Developer Program
Learn more here: www.scrum.org
Follow us on Twitter: #proscrumdev
Contact me: [email protected] or @rhundhausen
In stock at the TechEd bookstore!
What can we consider done?
Deliver business value each Sprint
Big design up front is waste
Delay requirements until last responsible moment
Only keep documentation if it delivers business value
Choose popular principles, patterns, practices
It takes smart developers to write software
http://northamerica.msteched.com
www.microsoft.com/teched
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn
Descargar

Document