May 18, 2014 Leave a Comment
Unscramble each of the clue words.
Copy the letters in the numbered cells to other cells with the same number.
May 4, 2014 Leave a Comment
The following words are all placed in the grid above. Find as many as you can.
April 30, 2014 Leave a Comment
Here is a link to the event on Google plus.
You can RSVP or just show up to watch on Friday at 2:00pm.
Here is a list of all the Uzility topics I will be training on.
See you there.
April 30, 2014 Leave a Comment
I get asked all the time, can Uzility be used for non-software projects? The follow-up question is usually: Can you change the column headings, add new columns?
My wife and I use a Uzility kanban board to track projects around the house. She has an idea that we need to remodel the kitchen, and I think we need to paint the family room. Over time we just establish a list of ideas that go into a column called Backlog. We then sort the backlog based on budget, available time, and time of the year. We have some pretty epic stories in the back log, like remodeling the kitchen, and some quick and easy items like Wash Windows, or rearrange the furniture in the family room.
We event have a second kanban board for family trips or activities. If my wife has an idea take the family on a ski trip to Canada, she just throws it in the list, and if I want to go fishing in August, I throw it in the list too. We sort the list, determine what we have time for, and what we can afford. If we don’t have time, or budget for a bigger trip, we just move a more affordable or shorter trip up the list to take the place of the one that is blocked. This has worked great, and has certainly improved the overall communication around trip planning.
With uzility we can change the columns to represent different workflows, for instance on the trip planning board we have the following columns Dreamboard, Planning, Booked, and Done. It is surprising how many trips or activities we have been able to move into the done column since we started using the system.
With either of these family boards we don’t have daily stand-up meetings, but we do have occasional backlog grooming and planning were we discuss and decide on what is next and how we are going to get it done.
April 29, 2014 Leave a Comment
T-shirt sizing is generally used to give more of a rough estimate in sizing, and are usually used before all the acceptance criteria are worked out on the story. The t-shirt sizing method allows the team who will be doing the work to give the product owner a wild guess of how large a task may be.
This can be useful in backlog grooming. Let’s say a product owner has 5 stories in their backlog, and that product owner doesn’t have any way to gauge the relative size between them. Additionally let’s assume that all the acceptance criteria haven’t been worked out yet either. The product owner is just looking for an idea of relatively how big tasks are.
When you are t-shirt sizing, it’s a good idea to keep it simple with only 4 sizes, Small, Medium, Large and Extra-large. Sometimes I hear comments like that’s an extra-small size, or I have even found myself saying that that user story will be at least 4 extra-larges, which isn’t the best practice. Anything that is larger than an Extra-large is simply too large to estimate, or is too epic.
You might have two very small tasks, one is to change a single misspelling in a word and you know exactly where the change is, one of those tasks that might take you 15 seconds to find and to fix. Then you may have another task that requires changing several files, and some more testing. Both of these tasks however compared to the others that you are estimating are small, and therefor are given the t-shirt size of small.
Only the people who could be doing the work should be allowed to provide t-shirt size estimates. The product owners and the scrum master should not be giving t-shirt sizes. I heard a funny comment from a product owner who stated that the team estimated it as a medium, but I rewrote the story as a small. I later learned that the PO did not talk to the team to get that small estimate, he just assumed that based on his changes it would be a small. This is very dangerous, PO’s should not be allowed to estimate t-shirt sizes or points.
While you are here, don’t forget to take a look at Uzility.com for Agile Kanban Boards.
April 28, 2014 Leave a Comment
I have just added the Product Tour Page to the Uzility site. Today I was asked several times for screenshots and details on the product that people can see before they register to create an account in Uzility.