It was a close game up until the last quarter, and I’m saddened that my team was not able to pull through.
Maybe next year…
I would be remiss if I did not do this…
“Go Cyclones! Beat the Hawks!”
Looking back on my first real-world project, I remember applying a lot of different agile and iterative practices, trying to get a feel for what worked and what didn’t work. Among those practices was the use of modeling UML diagrams (domain models, class and sequence diagrams) prior to actually writing the code.
What I discovered is that this task in itself can be applied using a variety of ways, from hand-sketching UML diagrams to whiteboarding to using a professional software tool. And each of these methods are better than others in the right setting.
This Ninja knows his stuff. And his answers and explanations are hilarious.
Even though I don’t have a video iPod, I still subscribe to this podcast and watch it on the computer.
From the title, it would sound like this post would represent a complete counterpoint to the basis of this blog. But I assure you, this is not the case.
Instead, I want to point your attention to an article from Siddharta Govindaraj. The article talks about five common issues that new adopters of agile may face when transitioning to an agile process, and what to do to avoid these dangers, including the need to actually understand agile before using it.
Agile and Iterative Development, by Craig Larman, is a book I recommend to managers, project leaders, and software developers who want to know more about agile. The book is clear and concise in its descriptions and provides many useful tips along the way to understanding agile.
It looks like the folks at Microsoft are definitely making progress with the new IE7 and its support for web standards.
While I still remain a Firefox fan myself, it’s nice to see that the effort to support outdated browsers will be lessened with this rather large step toward compliance.