• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Whose work is it anyway?
 

Whose work is it anyway?

on

  • 198 views

This presentation was for a workshop at the Institutional Web Management Workshop in 2005: http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2005/sessions/savory/ ...

This presentation was for a workshop at the Institutional Web Management Workshop in 2005: http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2005/sessions/savory/

From the abstract:

Dealing with external agencies for your web needs can be a frustrating experience - for you, as well as for them. Whether you're dealing with institutional IT services or a third-party company, there are many common problems that can occur.

This workshop will take a look at the issues involved in getting the job done, including:

* how to efficiently specify your work
* how to pick an external company
* how to check on and measure progress
* how to sign off and quantify achievements
* liaising between external companies and internal IT services
* dealing with ongoing support and maintenance

Statistics

Views

Total Views
198
Views on SlideShare
198
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Whose work is it anyway? Whose work is it anyway? Presentation Transcript

    • Whose work is it anyway? IWMW, Manchester, 6th July 2005
    • The problem...• Where to start it?• How to get it done?• Who should do it?• How to make sure it works?• What is ‘it’ anyway?
    • The problem...• Where to start it?• How to get it done?• Who should do it?• How to make sure it works?• What is ‘it’ anyway?
    • The solution?
    • The solution?• To be determined
    • Some thoughts...• Preparation• Problem definition• Resourcing• Progress• Completion
    • Preparation
    • What you need to know before you begin• Who is responsible for the project? • Do you have a project leader?• What’s the reason for the job? • Internal development? • Third-party deployment? • Bid-related?
    • About internaldevelopment...
    • Some suggestions• Solve the smallest possible problem. Incrementally.• Have the smallest possible team managing it (preferably one person).
    • About bids...
    • Writing bids• Does the awarding body have special requirements?• Be aware of all the issues• Get vendors / developers / technical advisors involved before submission
    • Defining the job• Scope• Timescale• Budget• Requirements• Users• External factors
    • Problem definition How to efficiently specify your work
    • Specifications• Should you be writing technical specs? • What’s the design methodology? • Monolithic / waterfall? • Agile? • Hit ‘n’ hope?
    • Specifications• ... or should you be trying to define the problem?• ... or what you want to happen?
    • Specifications, the XP way• User stories • Provided by you • ...often with help from the developer • ...or an analyst • ...or marketing
    • ResourcingHow to pick developers
    • Criteria for selection• Internal or external?• Contractor, employee, service, company?• Reputation, price, competence ...• The Google effect• The community effect
    • Selection process• Have a formal process defined in advance• Meet with them • Is an RFI/RFP/RFQ stage appropriate?
    • Criteria and questions• What is their background?• What similar work have they done?• What work are they doing at the moment?• What are their methodologies?• What is their normal daily rate?
    • Liaison• How to keep internal and external resources talking? • Introduce them to each other early on • Ask for policies/methodologies from both • Establish clear communications channels • Make conversation a default, not a decision
    • ProgressHow to check on and measure progress
    • Be involved• Release early, release often• Test in context• Check documentation• Measurable objectives: what are they? • feature-based? time-based?
    • Getting what you want• Change management• Issue and bug tracking• Iterations
    • CompletionHow to sign off and quantify achievements
    • Signing off• Have clear exit criteria defined at the start• Signing-off as continuous process• Do external evaluations early