SetH
Member
Registered: 15th Jul 01
User status: Online
|
Guys,
Doing some interview prep and struggling with the following question.
"development of work flow and knowledge base in order to meet the service delivery requirements"
I have not been involved in work flow develoment before but have good awareness of what a knowledge base is and how it works.
Can anyone explain work flow development, possibly within sharepoint?
Struggling to find any decent articles.
Thanks.
|
Daimo B
Member
Registered: 20th Mar 00
User status: Offline
|
Think workflows are literally just that. A set of processes and procedures to follow to ensure a job is completed to procedures.
Lookup ITIL as well as I think that covers the same thing.
|
SetH
Member
Registered: 15th Jul 01
User status: Online
|
Yes your right, it really is just that.
I did my usual and dived in at the deepend and starting looked at infopath and sharepoint etc.
Think I should be able to create a good answer to that now 
|
James
Member
Registered: 1st Jun 02
Location: Surrey
User status: Offline
|
Talk about this if you wanna sound really good:
http://msdn.microsoft.com/en-us/netframework/aa663328.aspx
|
Paul_J
Member
Registered: 6th Jun 02
Location: London
User status: Offline
|
quote:
Originally posted by James
Talk about this if you wanna sound really good:
http://msdn.microsoft.com/en-us/netframework/aa663328.aspx
Do you use TFS at your place James?
We use Team Foundation Server for all our source control, but we're now starting to move over to it for our work flow too.
So for instance a customer support operator can log in to the web interface, log a bug.
The bug can be turned into a work item and assigned to a software project.
The work item is then assigned / picked up by a team member on the development team.
The developer does the changes to the code and checks in the changes (I wont go into detail about the branching / merging process though).
The check in creates a change set against the work item, it triggers unit tests to fire and a automated build to occur.
The code now has annotation against it (or history) that those lines of code were modified by that specific coder, for the purpose of that particular work item (bug / dev).
The testers then take the work item and new generated build and test it works correctly. They can then append the work item to say it has passed the logical testing.
The work item is closed.
|
Paul_J
Member
Registered: 6th Jun 02
Location: London
User status: Offline
|
oh - incase you don't know about it james, the work items can be accessed within Visual Studio, so it means us devs dont need to bother checking a seperate web interface.
|
Paul_J
Member
Registered: 6th Jun 02
Location: London
User status: Offline
|
Seth if its for a company that does software, you can use the above as the work flow 
The only thing I forgot to say about is that previously logged bugs / documents / forums / information may also have been logged in the system (knowledge base) which for instance the person in support / dev could read to see if a similar thing has happened in the past.
|
Paul_J
Member
Registered: 6th Jun 02
Location: London
User status: Offline
|
Also Seth, you may want to research things like SCRUM if it is a development house... Creating a backlog list, prioritising them and doing sprints on a certain amount of items per duration... with daily meetings.
|
SetH
Member
Registered: 15th Jul 01
User status: Online
|
Cheers guys, got a much better idea how to prep for this one now.
|
Half Pint
Member
Registered: 25th Mar 02
User status: Offline
|
look at ITIL which is a known standard also Prince 2 although that is more project management.
|
Paul_J
Member
Registered: 6th Jun 02
Location: London
User status: Offline
|
That's the thing seth, there's workflows for all sorts of 'IT'... what sort of field is it a work flow for?
|
Half Pint
Member
Registered: 25th Mar 02
User status: Offline
|
quote:
Originally posted by VXR
Think workflows are literally just that. A set of processes and procedures to follow to ensure a job is completed to procedures.
Lookup ITIL as well as I think that covers the same thing.
bugger you beat me....
|
SetH
Member
Registered: 15th Jul 01
User status: Online
|
quote:
Originally posted by Half Pint
look at ITIL which is a known standard also Prince 2 although that is more project management.
Im a Prince 2 Practioner. Did an inhouse ITIL Foundation but havent taken the exam yet.
|
Half Pint
Member
Registered: 25th Mar 02
User status: Offline
|
not sure if this will help... probably not:
http://www.sharepointbuzz.com/archive/2009/02/06/beginners-guide-to-sharepoint-2007-workflow-development-preparing-your-visual-studio-2008-workflow-project.aspx
|
James
Member
Registered: 1st Jun 02
Location: Surrey
User status: Offline
|
Paul I used TFS in my old team. I didn't rate it to be honest. The work item management stuff was pretty cool but the source control was a real pain at times.
Have you seen TFS sidekicks?
Because a lot of more complicated TFS stuff can only be done via the command line, some company wrote TFS Sidekicks which give you a UI to the commands.
|
Paul_J
Member
Registered: 6th Jun 02
Location: London
User status: Offline
|
Yeah, we have to fire up the command line occasionally...
The branching structure is fairly overweighted and not ideal for all scenerios too.
What do you use now?
|
James
Member
Registered: 1st Jun 02
Location: Surrey
User status: Offline
|
We use SVN for source control and CruiseControl.Net for build management.
We don't currently have anything that does the work item management. Although I think we could do with something....
|
Bart
Member
Registered: 19th Aug 02
Location: Midsomer Norton, Bristol Avon
User status: Offline
|
Whats the difference between workflow and collaboration software?
|
