Win2003 Sharepoint Team Services + Sharepoint portal server 2003

[drkestrel]

I understand from the following Microsoft webpages that
Windows 2003 Sharepoint Services has risk/issue tracking
facility (in conjunction with Project Server 2003):

http://www.microsoft.com/technet/pr...skit/PRK_ssvrsharepoint_3538.asp?frame=true#7

http://www.microsoft.com/windowsserver2003/techinfo/sharepoint/whatsnew.mspx

I am struggling to find more information on finding any
more info on the Microsoft website on this and I don't
even have Windows 2003 installed at present.

A few queries:

1) My biggest query, from a business perspective, is
whether the list could (by default or could very easily
be configured) to capture Risks and Issues (seperately)
like what is shown at

http://www.ogc.gov.uk/sdtkdev/examp...preadsheets/Excel95/Risk & Issue Template.xls

2) How configurable/manageable are the issues/risk
list/log? Would it be simple ASP.NET programming? I am
just thinking about the following initially
2.1) Adding/removing columns to the list
2.2) Configuring projects (with different access rights
for different users on each project)

3)Also very curious as to why Risk/Issues Tracking is
bundled with Sharepoint, a document management service?
How/Where are the issues/risks stored?

4) Finally, can I use both Windows 2003 Sharepoint services
(for Risk/Issue Tracking and integration with Project Server 2003) and Sharepoint Portal Server 2003 (for document management and for managing contents within an Intranet Portal)?

 

[hogspawn]

Don't know if you have this sorted yet but I've few answers:

1. Point is that Project uses Sharepoint to Store its Risks & Issues, not the same as Sharepoint having a Risks/Issues handling capacity. I believe Project has a fairly clear idea as to what it sets up within Sharepoint, but I should think this is quite configurable.

2. I'd be surprised if you had to do much ASP.NET programming to do the configuration.

3. As I say, Sharepoint has no inherent Risk/Issues, Project has and uses Sharepoint as a repository.
They are stored in Sharepoint in an ordinary document library.

4. WSS and OSPS work together very closely. OSPS doesn't make much sense without WSS. WSS is a bit puny without OSPS.

Regards

 

[bsimser]

1) My biggest query, from a business perspective, is
whether the list could (by default or could very easily
be configured) to capture Risks and Issues (seperately)

You can create a custom list or even upload a spreadsheet into SPS to create the list quite easily. I took your list and compared it against the Issues template that SPS has and it's pretty close. You could take that as your starting point and add the custom columns needed in a few minutes.

2.1) Adding/removing columns to the list

Simple web interface, no programming required.

2.2) Configuring projects (with different access rights
for different users on each project)

You can use the template over and over in different sites and/or apply security to each list with little effort.

3)Also very curious as to why Risk/Issues Tracking is
bundled with Sharepoint, a document management service?
How/Where are the issues/risks stored?

Issues are just a list to demonstrate the different capabilites of a WSS site. The document management portion is just part of the whole Portal offering.

4) Finally, can I use both Windows 2003 Sharepoint services
(for Risk/Issue Tracking and integration with Project Server 2003) and Sharepoint Portal Server 2003 (for document management and for managing contents within an Intranet Portal)?

Sure thing. The WSS is really meant for collaboriting on information (like a project) while the Portal server portion is to view aggregate information about it and target content to specific audiences.

Hope that helps.