This is a project charter and management plan for this website: https://www.rey.wiki/george.

Crystalize a portfolio - Project charter

So far, I never needed to look for a job: the job was looking for me. The world has changed in 2020. Now, I need to put effort into finding a new source of income.

People of my kind normally have a list of publications to demonstrate. Myself, I have done a lot of interesting work and applications, but my ‘scientific publication’ record is poor; I have never placed much attention on that, being content with presenting to groups, and mentoring individuals.

• Update: I find that actually, there is at least 56 publications with my name on. This is because I have collaborated and contributed to many people’s work. An average of 4 publications per year is not bad!✔️ I can also claim credit for at least 4 publications where the main author “forgot” to add my name. Shame on them.

I decide that I could use a portfolio (“wiki”) to announce my abilities to future employers.

Stakeholders

• Myself - George Rey
• University of Strathclyde, including prof. A.Gachagan, and Dr Alexandru Moldovan
• Orestis Georgiou - my past mentor
• Brian Heaton - my mentor
• My past students
• My past co-workers
• Matthew Rey

High-level requirements

• Must list my achievements with several levels of detail
• Should include drawings, photos and videos where possible

Measurable objectives and success criteria

• There is something to be proud of for every year
• There is an entry for most events that I am able to find in my archives. Skip low-importance events.
• The structure is easy to navigate

Project exit criteria

What are the conditions to be met in order to close or to cancel the project or phase:

• None. This must be delivered, although it might take a long time, see the risks section.

What constitutes success

• All the requirements are delivered
• I get a satisfactory job

Requirements and Scope

• For each year since 2000, list something notable about my professional career.
• List the professional career events only.
• Write a list-form time-line with titles of events only, and put details into separate files
• Use markdown to write the content
• For each event:
  • Strive to put at least 1 screenshot or photo
  • Describe the why, the what, and the how, use the CAR model
  • List the skills learned and keywords
• Use markdown+GitHub or Jekyll to publish; alternatively, publish to my own hosting service.

Out of scope

These ideas I leave for later:

• Make a system where I can send someone a link that would only display a filtered list of events.
• Develop a system where one can filter by tags

Activities

• Rebuild my office and workstation.
• Refactor all my available archives into a single ZFS pool
  • Collate all archives into one structure
  • Triplicate for archival safety
  • ZFS archives verified safe and sorted
  • Some DVD-based are still outstanding
    • Missing: source code, screenshots, report, certificate for the 2004 “helix over spline” project. That was a great achievement!
• Sort the archives by professional/private and by year. Add date where possible.
• Convert my existing CVs to the timeline format. Create the placeholder detail files, but leave them mostly empty for now.
• For each year, select at least 2 events of interest, ideally 4+. Write a title.
  • 2020 done
  • 2019 done
  • 2018 done
  • 2017 done
  • pre-2017 done.
• Review my google-able publication list and absorb into my own wiki
  • Researchgate
  • Strathprints
  • Google scholar This is in progress
  • any other source?
• Promote the wiki site to my network
• For most notable events, and where more material is available, create a detail file.
• Research publishing options
• Adapt my CV and Cover letter to include references to the published version of the archive
• Adapt www.rey.wiki to feature the archive prominently
• Begin job search

Risks and mitigations

I might die.

• leave the rest to the entropy.

A fantastic job might find me before I am ready to use the result of this project to find one.

• Archive the entire thing for the next time it is needed

My computer might die

• send the working copies to github on a regular basis.
• Keep the relevant archives triplicated.

Human error destroys the progress

• send the working copies to github on a regular basis
• Keep the PC on so that backblaze does it’s job.

---

Meta

Created using https://obsidian.md/, and https://typora.io/, and adapted for use with jekyll where applicable. The intention is to keep it compatible with https://spec.commonmark.org/