Finally it was released…
The “Team System Work Items Basic User Guide” was released and can be downloaded from the codeplex project: “Team System Guides”
The guide can educate new and advanced users to better use the Work Items section.
I have already started to work on “TFS 2010 Work Items Basic User Guide” and I will start publish its parts very soon in my personal blog.
After the grate success we add on the Team System lectures we made in the ALM user group we are about to do it again on 11 of November, it will be half a day full of lectures regarding the new features of Team System 2010.
I will talk about the MTLB (Microsoft Test and Lab Management) that a new tool for the tester.
The lecture I have planed will benefit all the roles in the development process and not only for testers.
In order to register for the event (Its free) go to the following link:
Looking forward to see you…
I have recently announced the Team System 2010 overview lecture that will take place in the following ALM group in Microsoft, you can read more about it here.
I am about to talk about the “Testing” part of the lecture, were I will show the new tool for the testers – “Microsoft Test and Lab Manager”.
I hope you will enjoy it…
In July 13 2009 16:30 – 20:15 we are about to present the main features and capabilities of the Team System 2010 Beta 1.
The lecture will take place at the Microsoft office in Rahanana and will be opened to everyone.
Registration to the event is required there are a limited places so hurry up and take a place, you can read more about the event and register here.
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...
There where times when I believed that managing a good project involves only pure professionalism, but with time I found out that a good project manager should also have high social skills as well in order to be a good project manager or in that case a good manager in general.
Lets say that you need to deliver a project but the expected result varies depends on the stakeholder you ask, what would you do than?
This is a very difficult situation when you are about to fail no matter what the results of the project will be.
My advice for you...
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.
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...
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...
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...