We won the Gordon Pask Award
We're very pleased to receive one of this year's
Gordon Pask Awards.
We'd like to thank the people who are part of our adventure: The crew at
Energized Work who continue to inspire and challenge us; our clients, who have been courageous enough to try something different; and our friends in the agile community who have supported our endeavors. This award is for them all.
A few years ago we said companies valued the wrong things; businesspeople weren't accountable for their decisions; software development lacked craftsmanship; and people weren't empowered to do the right thing. Our '
No Compromise-
No Excuses' approach gained us a reputation as zealots. Yet to us, it was just a decision not to compromise on the
stuff we think is important.
Craftsmanship, personal discipline and rigor are important to us. But software is much more than code. We wanted to work with companies who recognized their software as assets and were prepared to push the boundaries, to change their organization and culture, to achieve greater effectiveness.
We're excited by the future - working with new companies, evolving our use of
pomodoros,
product streams and lean accounting to maximize client profit, and testing our ideas for user-driven development. Rest assured, we'll continue to challenge the status quo and we'll continue to learn and improve.
Thank you all very much.
Links to this post
We'll finaly get around to finishing the
Energized Work web site in September. In the meantime I wanted to share a glimpse of the design. It's been a great journey with
Tim Nicholls at
Electric Light Box, as we captured our
attitude and
ethos in this 'comic book' feel.
A new dawn, a new day. As they say. And every day we continue to experiment and improve
The Energized Way.
Links to this post
Thinking out loud about users, behaviour and acceptance tests
I want to play more with the combination of
behaviour-driven development and
Selenium IDE. Stuff isn't clear in my head yet and I'm not entirely sure what I'm aiming for. Maybe it's that, given my interest in usability and interaction design, I want greater emphasis on the user in our acceptance tests.
Am I seeing a Selenium test demonstrate the achievement of a user's goal, broken down into the user's actions expressed in plain English that map, under-the-hood, to Selenium commands?
Questions I'm asking myself: How do these tests relate to the acceptance tests on the back of the story cards? Are they the only tests on the back of the card? If they're not user-focused their 'internal', right? Are there other kinds of Selenium-based acceptance tests, perhaps within a hierarchy, which don't focus on the user? Are these aceptance tests?
Um ...
Links to this post
Scrum Mastering isn't a part-time endeavour
Don't be a part-time scrum master because 'you can't see the picture when you're in the frame'.
Links to this post
