Search

Categories

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Send mail to the author(s) E-mail

# Monday, 08 December 2014
( Agile )

CTO of Telerik.  Board member of the Scrum Alliance.
@worksonmypc

Stand on the shoulders of giants (a lot of his presentation was based on the work of: User stories applied / Mike Cohn

These are my notes from Stephen’s presentation

http://www.pluralsight.com/author/stephen-forte – Courses on Pluralsight (including Agile Estimation)

https://t.co/ZCS2F6xnvF

image

The Cone of Uncertainty!
http://blog.codinghorror.com/the-mysterious-cone-of-uncertainty/

“The cone of uncertainty… is that early project estimates will always be wildly inaccurate”

Based on 50 years of data on software development.

How to do better?

  • Have ‘stories’.. As a… I want to… In order to…  to keep focussed
  • Estimate toughness of each story
  • Have a list ‘backlog’ of stuff to do and what I’m doing in next few weeks
  • Keep on estimating after each sprint, and communicate back to client so they have no surprises

This means that:

  • Know our release dates
  • Will know what features will make it in as development proceeds

Tips

  • Iteration 1 always goes wildly wrong (figuring stuff out)
  • 5 iterations to get trust with client

http://blog.codinghorror.com/the-long-dismal-history-of-software-project-failure/

| | # 
# Monday, 16 December 2013
( Agile | Craftsmanship | Dojo )

http://www.youtube.com/watch?v=yao5XLJqogQ
http://pluralsight.com/training/Courses/TableOfContents/the-coding-dojo

Agile Manifesto

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

Software Craftsmanship

  • Well crafted software
    • compact
    • elegant
    • clean
    • uses Design Patterns
    • has comprehensive unit tests
  • Steadily adding value
    • emerging design
    • refactoring
    • comprehensive automated tests (check havn’t broken anything)
  • Community of professionals
    • trust
    • respect
    • always learning from each other
  • Productive partnership
    • trust
    • understanding mutual goals
    • communication enhanced by executable specifications

XP Practices

image
TDD in the middle!

How to get good at TDD

  • Pair program
  • Coding Dojos
    • Roman numerals
    • Minesweeper
    • prepared kata
      • start with empty editor on screen and do tdd
    • randori
      • everyone contributes
      • split into pairs or all work together
| | #