יום ראשון, יוני 7, 2009
I have seen many answers to this question, all talking about matrixes, what should I test, How should I test etc.
Not many answers to this question talked about the overall process of development, the bigger picture…
The testing process is part of much bigger picture of development that involves the developers, testers, managers, stockholders, marketing and more.
Lets start with what stops the development in general, that will be the time to market of course, no product no matter how good it is will worth anything if it wont be sold.
When we come to manage a project we slice the time...
יום רביעי, מאי 20, 2009
For all my customers that kept asking me when it will finally be here I am glad to say after all this exhausting waiting for it, it is finally here!!!
The official announcement was two days ago 18/05/2009, you can read more about the release in Brian Harry’s post here.
I can’t wait to start using the cool feature in this release and I am sure I am not alown.
יום רביעי, מאי 6, 2009
We have seen that our little bug was caught and documented on the last Bugs Life post, if you didn’t read that yet you can read it here.
Today I have got my verdict, Obama the Project Manager has decided to “Fix” me.
They say that it will be expansive to “fix” me but it will cost more to leave me unfixed, they say that this part of the software is not a critical part but still will be used by part of the customers and loosing there trust will cost more than the “fix” cost.
Dennis the programmer said that...
יום שלישי, אפריל 28, 2009
I have recently posted about bugs in: Are All Bugs Should Be Fixed? there I promised to post about how to manage bugs.
How to manage bugs is a little boring subject so I will try to explain it in a different way.
I will quote from a bug’s diary in the “Bugs Life” posts so we can understand what happens from a “bug’s perspective”, I will add my own explanations to it so we can understand the process.
I hope you will like it, lets start…
This diary has been written in what our bug describes as “Jail” which is what we...
יום שלישי, אפריל 7, 2009
The answer is 2 – 5 days!
I am working with a lot of project managers and team leaders and when they show me there project plans I see tasks that are half a day, a day and many times I see tasks that are more than a week.
I like to clarify a few points before I continue:
When talking about tasks I talk about any type of task, for example tasks for testers, programmers, IT etc.
There are tasks that are estimated to more than 5 days, these are high level tasks that will be divided later to smaller tasks. It...
יום חמישי, אפריל 2, 2009
I have published a post regarding the Scrum Process Template here.
Now I like to talk about a grate addition to the Scrum with Team System.
In CodePlex there is a project name Scrum Sprint Monitor located here.
This project is a screen saver that shows you the Sprint status at all times with nice summaries, graphs and charts.
To set it up you need to do the following:
Step 1: Edit the “SprintConfiguration.txt” file
Here is an example:
ProjectName= Scrum Example ProcessTemplateName= Scrum for Team System 'IterationId= 162698 IterationPath= Scrum Example\Release 1\Sprint 1 'BuildDefinitionName= <CI Build Definition Name> SprintStartDate= 2009-3-18 10:00:00 -6:00 SprintEndDate= 2009-4-18...
יום ראשון, מרץ 15, 2009
The answer to this question is defiantly NO!!!
All bugs should be managed but not all bugs should be fixed.
Many times when I talk with my customers about the way they develop software I hear the wrong concept of fixing all the bugs before the release.
So why not to fix all the bugs? An application without bugs is not better than an application with bugs?
Well lets start with a very important fact: There are no applications without bugs, there are applications that have unfound bugs.
But we still left with the bugs that we have found why not to fix them...
יום חמישי, מרץ 12, 2009
Not once I am being asked the following question:
“Lets say that we have an active requirement that is assigned to a programmer, now the programmer is doing the design and the code for the requirement can I close\Resolve the requirement as done? what if I have bugs that are active and related to this requirement?”
First I like to start by saying that a requirement can be Resolved and then be closed or can be Closed without being resolved first depends on the methodology being used, for our discussion it will be the same result, the requirement is marked as...