I made the trip down to Austin for the second stop of Stack Overflow Dev Days. I had a great time even though I barely had time to enjoy being in Austin itself. I met a lot of interesting folks and was impressed with the crowd as well as the speakers. It was a busy day, so I will recap individual parts of the day.
The first Stack Overflow Dev Days conference kicks off this morning in Boston. Joel is set to unveil 4 products in his keynote.
My guess would be that StackExchange leaving beta might account for one of the four. Kiln, whatever it really is, should also be announced and explained. What other treats await us?
Oy vey! So, Spolsky and crew have been playing coy as usual with their latest product announcement: Kiln. So what do we (think) we know about this?
Daniel Root provides a nice look at how he implements Scrum with FogBugz 7. And I have to admit I didn’t know about his tip about entering estimates from the list view. Now I’m wondering if that is new to 7 or if I’ve just missed it all of these years.
I think it would be interesting to see how folks are using the Backlog plugin which Daniel does not appear to use.
Any other Scrum stories out there with FogBugz 7?
In lieu of a strict feature review of FogBugz 7, FogFanz will attempt a pseudo-philosophical look at the importance of the latest release from Fog Creek Software. And we poke a stick at the only competition we would consider using.
If you have not heard, FogBugz 7 is out the door. I’m sure there will be some official words from Joel and the Fog Creek crew soon. In the meantime…
Daniel Root has provided one of (maybe the first) review of FogBugz 7. If you were not involved with the beta, then this is a good place to go to see what FogBugz 7 has for you.
Daniel Root’s FogBugz 7 Review
As more reviews roll in, I will try to keep a list going here.
I’m in the middle of my own software release in the coming days, so I’m not going to tackle a full review just yet. But I will provide a mini review of FogBugz 7: I underestimated how useful the sub-cases and tags features would be.
Just a update on this blog and the world of FogBugz in general.
So, like a lot of folks I’ve been reading up on the recent announcement of Google Wave. I’ve been trying to figure out if and where this new tool from Google will be useful. Admittedly, it looks pretty neat but I’ve got my doubts.
But then I had this thought, what if Google Wave was embedded in the FogBugz case editor?
I am interested to hear how others are using FogBugz to perform a formal (or maybe informal) Quality Assurance role for a software team. The basic question is…
How do you use FogBugz to account for the QA process on your team?
There are a handful of questions that I have faced at work and I suspect many of you have too. This list is not exhaustive, but hopefully it provides enough context for discussion.
Note 1: Obviously, your development methodology will have a significant impact on your answers. I expect Agilist, for example, to have a unique approach.
Note 2: I will try to use “FogBugz” terminology for the most part. So, by “release” I mean a release as defined by FogBugz.
- Does your FogBugz case list include distinct entries for QA?
- Do you use a distinct QA/hardening/stabilization release?
- Do you create a “master” Scheduled Item case for QA of a release?
- Do you create a Scheduled Item (QA) case for validating each Feature case?
- Do you create a Scheduled Item (QA) case for validating each Area of a release?
- Do you set estimates for your QA cases?
- If so, do you use EBS?
- Do you rely on the Resolved vs Closed status to distinguish between cases that have been QA’d and cases that have not been QA’d?
- If so, how do you handle regression testing later?
- Do you use a different product to manage the QA of a Release?
Thank you, in advance, for your help. You don’t have to answer each (or any) of these questions. I’m just looking for some insight into best practices for QA with FogBugz.
This is all over Twitter so it is probably not news to most people that would find their way here. But Fog Creek has opened up sign-ups for the FogBugz 7 beta.
I’m going to cross-my-heart and promise not to blog away secrets…
https://shop.fogcreek.com/beta/
Congratulations to the Fog Bugz team for making it to this point. I’m sure they are as ready for some of us to stop yapping as we are to see their latest work.
UPDATE (4.27.2009): This weekend Joel shared this really good news via Twitter…
FogBugz 7 beta finds fewer bugs than expected, so we’re on track for another beta Friday and shipping well in advance of planned date
