Category Archives: Agile

Intro to fluency with TDD

Posted on by
Reply

Info

Breakout Session :: 300 (Advanced) :: Developer Practices

“In this demo-filled session, you’ll learn the why, what, where, when and how of working with test-driven development using the tools provided in Visual Studio 2010. In addition to seeing ‘testing-in-action’, you’ll learn about when to use what kind of test. You’ll learn both about using TDD with new code and in legacy situations. Code better and discover features in Visual Studio, such as code coverage and more that will help you to be more productive.”

Highlights

The session centered around fluency in TDD, and the requirement to keep your test code of production quality (i.e. refactor where necessary, etc.) – it also introduced the “Approvals” library, as an alternative to having to assert very granular bits of state.

The testing cycle suggested is: Whiteboard (Requirement), English (Translation), Code (Implementation), Test (Regression) and Result (Verification) and aims to promote the notion of “Intentional Code”.

Links

Using Tests to drive the entire SDLC

Posted on by
Reply

Info

Breakout Session :: 300 (Advanced) :: Developer Practices

“Given that you want to deliver high quality code, when you drive your entire software development lifecycle with tests – you will dramatically improve overall quality. Microsoft’s introduction of Visual Studio 2010 and Microsoft Test Manager provides very powerful tools we can use to begin with tests. In this presentation we specify an entire system with tests. We begin with tests to ensure the business value of an application is testable and we know when we’re done. Using those tests, we clarify the requirements using acceptance criteria expressed as test cases. Finally, we decompose the requirements to specific testable behaviours that will drive our unit tests. Armed with the complete understanding of the application, we begin to work upwards again. We automate the unit tests to ensure our code is tested. Then, as our code begins to take shape, we automate the functional tests to ensure our requirements are met – and stay met as our code continues to evolve. Finally, we automate the system and integration tests to prove to our customers that we have met the end-to-end vision of the application. The final demonstration shows the integration of all tests running during an automated nightly build.”

Video

Agile Anti-Patterns!

Posted on by
Reply

Info

Breakout Session :: 200 (Intermediate) :: Developer Practices

“The popularity of agile software development processes and methodologies is imminent and fast growing. Many organizations and projects turn towards agile to help solve the problems of traditional software development. Scrum, extreme programming, test driven development, and lean are no longer the new kids on the block. However, with the rising popularity of agile, mainly due to lack of experience or management over-expecting results, in coming years many agile projects will fail miserably. Agile is not the silver bullet.”

Video

Highlights

List of Anti-Patterns:

  1. Traditional approaches are evil
  2. Velocity is unimportant
  3. Senior guy estimates the work
  4. Open plan office and cubicles
  5. Missing product owner
  6. Mini waterfall
  7. Change iteration length
  8. Changing requirements intra-sprint
  9. Task boards are old school
  10. Documenting everything perfectly
  11. Pick the low hanging fruit