
Originally Posted by
english_learn
The below diagram below explains how a real change request has been handled in TFS. ("has been" refers to the past. This form can be used if you are pointing out how something was done in the past. If you are discussing how things are done in the present, use, "is handled...")
As you can see in the diagram, there is a main/parent work item created for this change.
Look at No. 1 in the diagram.
This work item has full details of the change request, such as the reason for the change, impact analysis and so on. The work item is also linked with some existing work items, which are affected by the change request. Look at No. 3 in the diagram.
In this scenario, some requirement and design documents will be updated/modified and, therefore, some new work items have been created to track them. (Look at No. 2 in the diagram). So, at any point in time, changes made to relevant documents easily can easily be identified by looking at the history of these those work items.
This structure is also very helpful in generating an ATM report. If a query is triggered, based on the parent work item, it will show all change related work items with descriptions as below.
The Australian government has introduced a tax on cigarette companies. Currently, cigarette companies pay a 70% tax on their sales. As a result, recently, the price of the cigarettes has gone up. But still, there are thousands of people addicted to smoking and are spending a huge amount of money in on it. The government is keeps influencing (The fact is that they are not influencing the public - they are trying to educate the public or they are telling the public, or they are trying to influence the public. If the govenment influenced people, people would change their habits.) the public in as to the consequences of smoking. However, most of them are not listening and keep smoking. Some are believe that the human life time is already fixed by God and habits like smoking is will not change the their life time.