Developer's Checklist: Taking over a project

So I'm starting to get the impression that I no longer tender for brand new projects competing with time and cost in order to win the bids. Recently, more and more people have been asking if I can take over a project that has been abandoned by its developer.

I've started writing this article because I find myself forgetting to ask something that could have saved an infinite number of man-hours (I exaggerate a little); but seriously, I needed a checklist that works for me.


Most Difficult?
My hardest project was (still is) one created by a PhD student who graduated and left the institution. It was a custom-built site written from scratch, and it's purpose was to manage Staff and Students within the Additional Learning Needs group. These are staff who take lecture notes for people of all disabilities and assist the students for the duration of their course. It had to allow for synchronizing with the official student record system and timetabling system (done via file upload). It included it's own timesheet / session management / invoicing system.

The website was held on a virtual host running PHP and MySQL. There was no documentation, logs, notes, and any code comments were in Hungarian (later found out it was slang or a dialect not understood by most Hungarians). Fellow students and system administrators could not accurately describe what the system was for and what it does. The developer had created the system to only last during one academic year, and the system itself only just about understood academic years (required tweaking twice a year). Then there were the error logs... some 20000 errors per use of a feature over 4 seconds. Do some developers never check the errors log?

By the time, I started maintaining the project, a revamp had been agreed with another web team. This has been delayed somewhat and still after 2 years there is no new site (blamed on the customer for not knowing what their application did in the first place... tut tut. How long have you been a developer? And this is new?).


Can the developer be contacted? Yes!
  • Questions to ask the developer

    1. The original client's brief for the project?
      (project mandate/charter/initiation document - the spec)

    2. Details on the Development Environment
      (is there a TEST system and deployment procedure in place?)

    3. Known Issues/Bugs
      (is there an "Issues Log"? Anything that still needs addressing?)

    4. System Requirements
      (in case you need to transfer/move to another server)

    5. Critical functions used in the system?
      (do this yourself anyway and use theirs as a guide only)

    6. Site Authentication Method(s)
      (will this need to be rewritten? eg. clear-text passwords)

    7. Level of Security Testing
      (XSS and SQL-Injection at least?)

    8. Referenced common files / global assets
      (especially those used in every page)

    9. Expert/Testing/Resistant users
      (contact details and informally their technical knowledge/skills)

    10. Availability via Phone/Email/In person?
      (not relying on this but it can save time... sometimes)

  • Service Transition

    1. Security rights/roles in the system
      (reasons for different accesses)

    2. Get all known logins
      (database, ftp, sftp, ssl, site logins: test & admins)

    3. List all files, their purpose
      (consider a spreadsheet of all active/legacy files)

    4. Get new brief from the Client
      (agree on maintenance & development costs/time -> custom timesheets!)

    5. Check domain name is registered/transferred to the client
      (quite a biggy - gives the client an exit strategy)


Can the developer be contacted? No!
  • Security Check

    1. Usernames/Passwords
      (formats, defaults and vulnerability)

  • Technical Review

    1. Examine all functions: what goes in, what comes out?
      (accepts/returns, data types specifically, test by running each function separately)

    2. Examine databases
      (data types, constraints, primary/foreign keys, autoincrements, schema diagram, scheduled jobs)

    3. Examine content integrity
      (what is available front-end and back-end? can it be circumvented?)

  • Website Revamp?

    1. Signed Off Specification
      (describing clearly the agreed work to do and expected results)

    2. Realistic Cost & Time
      (obviously agreed with client)

    3. Additional Documentation
      (timesheets, agreements, technical specifications, issue logs, product documentation)

  • Security Check

    1. Usernames/Passwords
      (formats, defaults and vulnerability)

  • Check ALL server-side errors
    1. EventViewer (if Windows)
    2. errors.log (if Linux)

Above and beyond
  • Product Handover
    (branded pack with contact details - make it simple and friendly!!!)

  • Warranty / Grace Period
    (agreed support period post production - fees and estimates)

  • Behind the scenes
    (code comments, user-defined function headers - incl. author, name, purpose, receives/returns)

Anything to add?
I welcome any suggestions/improvements to the above. Just add a comment to this page. Also if you want to share your nightmare project takeovers, they're always fun to hear about.

Credit where Credit is Due:


Feel free to copy, redistribute and share this information. All that we ask is that you attribute credit and possibly even a link back to this website as it really helps in our search engine rankings.

Disclaimer: The information on this website is provided without warranty and any content is merely the opinion of the author. Please try to test in development environments prior to adapting them to your production environments. The articles are written in good faith and, at the time of print, are working examples used in a commercial setting.

Thank you for visiting and, as always, we hope this website was of some use to you!

Kind Regards,

Joel Lipman
www.joellipman.com

Related Articles

Joes Revolver Map

Accreditation

Badge - Certified Zoho Creator Associate
Badge - Certified Zoho Creator Associate

Donate & Support

If you like my content, and would like to support this sharing site, feel free to donate using a method below:

Paypal:
Donate to Joel Lipman via PayPal

Bitcoin:
Donate to Joel Lipman with Bitcoin - Valid till 8 May 2022 3QnhmaBX7LQSRsC9hh6Je9rGQKEGNQNfPb
© 2021 Joel Lipman .com. All Rights Reserved.