Hi Justin,
Thanks a lot for valuable information, I am with your
about dividing the project to releases which is the case what I am
looking for, but I have some points I want you to reply since you
already use this way to divide your projects in TFS :
1) As long as you divide the same project into releases, the
project is getting complex this is first, and you have to customize all
reports in your project to take care the Release/Version into
consideration, since you can work on both version on the same time.
2) Customizing the reports is not the only problem, what about the
Managing the Different Documents for different releases ?
3) Suppose that the project has been customized, how can I
customized the reports which will shown in the Project Portal which is
the most important KPIs for Management Level.
Lets share this ideas with all to see different view for this issue, and
this can yield to better Project Structure of the future releases of TFS
?
Regards,
Mostafa Arafa
http://moustafa-arafa.blogpost.com
MCSD,MCTS,MCT,C# MVP
<https://mvp.support.microsoft.com/default.aspx/profile=AD272725-2AE3-42
C6-9AFC-89A75A7A5197>
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Butcher, Justin
Sent: Friday, May 18, 2007 2:44 AM
To: [email protected]
Subject: RE: [OzTFS] Best Practise in managing TFS Projects
[SEC=UNOFFICIAL]
Mostafa,
We've given this a bit of collective thought where I work. TFS is used
by a large (and growing) number of teams across many platforms,
technologies, geographic locations and political persuasions within our
organisation. There are no easy answers that cover every situation.
We are taking the view that our team projects will be based firstly
around our software products, then secondly around the projects or work
initiatives that go into producing the software.
What that means is that our project structure looks like this
<Software Product> (Team Project)
<Release or Version> (Folder - usually maps to a specific
set of tasks making up a development project
<Technology Platform> (In some (ideal) cases
this split won't make sense but in cases where there is a strong team
split based on platform we'll work this way.)
<Branches, Folders, etc>
We're aware that this might mean that at some point a team project might
get so full of work items, reports, etc that we'd need to start again
with a new Team Project, but what we're aiming for is a top-level view
that reflects the software products, so that people across our (large ad
dispersed) organisation can browse software products that fall outside
there primary scope of work easily. We're trying to think about what
TFS store will look like in 5 years time, and organise things so that it
will make sense even when the current crop of developers have moved on.
There's no easy answer, since software products merge and split due to
business requirements and for technical reasons. But generally we think
that that's the view we'd want to have in 5 years from now, rather than
a view that primarily shows project initiatives.
Hope this is of interest.
Justin.
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Mostafa Arafa
Sent: Thursday, 17 May 2007 18:24
To: [email protected]
Subject: [OzTFS] Best Practise in managing TFS Projects
Hi All,
In case you have a project, and you want to create a new
release of the same project.
Implementing the branch concept is ok from the source safe ,shall I
create a new project for it or I can use the same one ?
What I can say ,the TFS doesn't support the different releases concept
in project level, that's why we need to create a new project for each
new relase, especially if you have different document, security,
reports....etc.
Regards,
Mostafa Arafa
MCSD,MCTS,MCT,C# MVP
<https://mvp.support.microsoft.com/default.aspx/profile=AD272725-2AE3-42
C6-9AFC-89A75A7A5197>
********************************NOTICE**********************************
***
This transmittal and/or attachments have been issued by Agility. The
information contained here within may be privileged or confidential. If
you are not the intended recipient, you are hereby notified that you
have received this transmittal in error; any review, dissemination,
distribution or copying of this transmittal is strictly prohibited. If
you have received this transmittal and/or attachments in error, please
notify us immediately by reply or by telephone (Tel. +965-809-222) and
immediately delete this message and all its attachments.
****************************************************************
IMPORTANT
The information transmitted is for the use of the intended recipient
only and may contain confidential and/or legally privileged material.
Any review, re-transmission, disclosure dissemination or other use of,
or taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited and may result
in severe penalties. If you have received this e-mail in error please
notify the Privacy Hotline of the Australian Taxation Office, telephone
13 28 69 and delete all copies of this transmission together with any
attachments.
****************************************************************
OzTFS.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject.
Powered by mailenable.com - List managed by www.readify.net OzTFS.com -
to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject.
Powered by mailenable.com - List managed by www.readify.net
********************************NOTICE*************************************
This transmittal and/or attachments have been issued by Agility. The
information contained here within may be privileged or confidential. If you are
not the intended recipient, you are hereby notified that you have received this
transmittal in error; any review, dissemination, distribution or copying of
this transmittal is strictly prohibited. If you have received this transmittal
and/or attachments in error, please notify us immediately by reply or by
telephone (Tel. +965-809-222) and immediately delete this message and all its
attachments.
OzTFS.com - to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject.
Powered by mailenable.com - List managed by www.readify.net
