Wonderful time. Again. The Agile Testing Days guys are doing a wonderful job, creating a magical, friendly, family-like conference. Awesome job. I’ve done a tutorial, a workshop, a lightning talk, ran a story telling game, joined a powerpoint karaoke and, oh yes, wrote a poem. Here are the slides from the very funny, killer pony
The agile manifesto says we value working software. What is working software anyway? We can talk about software working in different contexts. First are the non-tangible parts (more working than software): Idea – The ideas for the product we’re going to build need to make sense and solve the our customer problem Design – We
When I first took on product management, I started learning techniques, like understanding the market, strategy, SWOT analysis. While I didn’t write “proper” user stories, I prioritized requirements, and was there for the team to describe scenarios, answer questions, update on news, test the application and give feedback. My time was split between doing “product management”
Great fun, and it requires 2 hours, not 1.5 hours. Here are the slides.
The videos are up on the Everyday Unit Testing site – “TDD Patterns” and “Creating a unit testing strategy“. Check’em out!
A new post, on the anti-patterns in unit testing has arrived on EverydayUnitTesting.com! This time we’re talking about tests imitating code, or in a more catchy name: Code matching. Check it out!
I’ll be at Agile Greece this year! In addition to the “Advanced Agile Programming Techniques” workshop, I’ll do the new, improved and highly Star-Wars enabled “Why TDD is important for everyone”. First, get your ticket, and then enjoy this interview about those topics and Star Wars.
Last week I had a very interesting session. My dad and his friends have their own meetup, when they invite speakers to present topics of all kinds. I presented this week. While some of them did have ties to the tech industry, the topic was how organizations are built, and how they work. Why they are
Continuing the series of anti-patterns in the wild world of unit tests, this time we’re exploring writing logic (conditionals, for example) in tests, and why it may not be a good idea.
“Everybody, please, stand up”, I remember encouraging everyone to rise to the occasion of another daily stand-up “meeting”. Even with a room full of people who knew the drill, I still felt I had to ask them. With every practice we do, we anchor around one or two basic assumptions, we believe will help us achieve the