Samples of My Work

Project 1: Documentation Example

Below is the Order Automation Overview Table of Contents I created for the fictitious Sample Company.

Before creating documentation, I first meet and align with document owners on what artifacts are being created, for what purpose, for what audience.

I then outline a high-level draft of what the document will contain, and get agreement from owners before adding content to each section.

Project 2: Process Mapping Examples

Below is a Level 1 (High-Level) process flow diagram – without user personas – that I created for an automated Order Entry process.

Below is a Level 1 (High-Level) process flow diagram – with user personas – that I created for an automated Order Entry process.

Below is a Level 2 process flow diagram – with user personas – that I created for an automated Order Entry process.

Below is a Level 3 (Detailed) process flow diagram for step “4.4 Analyze Sales Order” from the diagram above.

Project 3: Epic and User Story Examples

Below are the high-level Releases for the Epic to “Process Orders Submitted via Email”

• Epic: 4.0 Process Orders Submitted via Email
  1. Release 1: Process Order Without Errors – Happy Path
  2. Release 2: Kick Out Orders with Any Errors
  3. Release 3: Handle Order Header Errors
  4. Release 4: Handle Order Detail Errors

Below are the titles of users stories for Release 1.

• User Stories for Release 1: Process Order Without Errors – Happy Path
  1. Identify and Log if File Has Errors
  2. Happy Path: Break Order Into Logical Chunks
  3. Sign in to Legacy System
  4. Navigate to Order Entry Screen
  5. Identify Number of Order Headers
  6. For Each Order Header, Enter 1 to Many Order Details
  7. Log After Entry of Each Header is Complete
  8. Log After Entry of Each Order Detail is Complete
  9. Log After File Processing is Complete

Below is the text of User Story 9.

• User Story 9: Log After File Processing is Complete (using Gherkin Syntax)

Given an order file was emailed in

and received by Sample Company

and automation analyzed the order

and automation determined the order could be processed

and automation signed in to the legacy system

and navigated to the order entry screen

when automation has successfully entered the order header

and successfully entered all order details

then automation logs the time datestamp the order was entered into the ORDERS database in the CREATEDON field (in the format: mm/dd/yyyy hh:mm:ss – example 12/30/2020 10:15:55)

and logs the order number (pulled from the legacy system screen) into the ORDERS database ORDERHEADER field.

Project 4: Creating Priorities, Objectives, and Key Results (OKRs)

Below I followed the pattern of “Measure What Matters” author John Doerr (link) and created a short presentation on the Priorities, Objectives, and Key Results (OKRs) for Sample Company’s Sales Team.