This is the 1st principle of the Agile Manifesto from the year 2001 that you can find on http://agilemanifesto.org/
As a developer you come to the point in time where a manager asks you to have at least 80% Code Coverage in your code.
Photo Credit: Sam Foster
All managers love to see numbers, especially big increasing numbers.
I love big numbers too!
After publishing the paper on scrum.org here, I wrote a german version for the dotnetpro magazine of January 2013.
Check it out!
And make sure to buy the magazine!
I almost forgot to publish this recording here…
Figure: My talk on youtube http://www.youtube.com/watch?v=De8YTVxWGRc
- How often do you release your product to your end users?
- How often do your end users see and use your product?
- Do you release in sync with your Sprint length, after the Sprint Review?
- Is the Sprint Review meeting the only valid release point?
- When do you plan your releases?
See how the cadence of Scrum and Continuous Integration can help you build the right thing, and when implemented properly, release it on time to ultimately deliver superior value to your customers.
What caught my attention recently: Efficiency vs. Effectiveness
Figure: Early enough to learn to code efficiently. flickr
*Updated* 21 March 2011: Updated how "Coded UI tests" finds a control with info from Balagans Blog - How does “Coded UI test” fin...
If you get this nice error message, you are probably lost, because there is no hints on WHY!!!??? Microsoft Visual Studio ------------...
I am *very* keen on automating tests, so I was looking into unit testing a WCF service. If I say "unit test", I mean a fast ,...