PTO Calculator Capstone Project

example_story.md

Example Story

As a Crafter, I want to know how many PTO days I have left this year so that I can plan for my upcoming vacation.

Acceptance Criteria

Given that I am a first year Crafter
And I started on January 1st, 2019
And I have not taken any holiday
And today is July 1st, 2019
When I check out my PTO balance
Then it should say I have 14 PTO days

features.md

Potential Features

• Display PTO
• Enter start date
• Enter current job title
• Enter job title history
• Set base accrual rate
• Set accrual rate based on job title
• Set accrual rate based on tenure
• Set carryover date
• Set maximum carryover
• Set reset date
• Handle negative balance

logistics.md

Timeline

• Start date: July 1st, 2019
• End date: July 12th, 2019
• Code submitted by: July 11th, 2019

Review Board

• Bjorn Johnson
• Connor Mendenhall
• Damon Kelley
• Li-Hsuan Lung
• Sarah Sunday
• Steven Kwok
• Thomas Countz

Consultant

• Breanna Reader

pto-calculator.md

Capstone Project

This is largely based on Lunch Rotation Capstone Project, which is inspired by iOS Capstone Project and Capstone Project. This contains a guidelines for doing a project in this format, as well as specifics in how this project was presented to the apprentice, Olga Boiaryntseva.

The apprentice has two weeks to plan, implement and deliver the project, and give a presentation that includes a demo and discussion about technical decisions she made throughout the process.

---

The primary objective of the capstone project is for the apprentice to show that they are ready to join a client project as a Crafter.

Code Project: Show 8th Light employees how PTO is calculated

Planning a trip can be stressful, especially when you are not sure how many PTO days you have left for the year. This project aims to unveil the mystery around PTO calculation, and give 8th Light employees a peace of mind when they plan for their next dream holiday.

Project Requirements

• Work with the customers to create a Lean Canvas.
• Work with the clients to flesh out stories and prioritize them.
• Choose any language and framework to build the application.

Process guidelines

• Stories are available in a centralized location (Trello board)
• Work with the customer to get clarity on stories or issues that come up during implementation. A new channel called #pto-calculator is used for this.
• Send out an agenda for the presentation ahead of the review board meeting. The agenda should also include links to the lean canvas and the code repository for the members of the review board to review.
• The rest of the process should be driven primarily by the apprentice.

Presentation

For the day of the review board, prepare to talk about your code project. This presentation should include:

1. Overview of the documents: Cover the lean canvas.
2. Overview of the Trello board: Walk your audience through the Trello board you’ve been working through, and please make sure that it is up-to-date.
3. Demo: Give us a polished demo of the project that you’ve been working on. Please make sure that this shows off all of the features you’ve incorporated.
4. Discussion: Discuss the process of creating your project, specifically how you made decisions. This discussion can include a slide deck or a peek at your code, but it doesn’t have to, as long as your audience is engaged and your message is clear. 8th Light teams must communicate well with one another—use this presentation to demonstrate how well you can communicate with your colleagues and teammates. Please make sure to touch on the following topics as part of this discussion:
   • How did you prioritize the stories you worked on?
   • Why did you made the design decisions that you did?
   • What technical trade-offs did you encounter? Why did you make the decisions that you did?
   • What were some issues that you encountered and how did you approach them?
5. Q&A: Be prepared for a Q&A session at the end, in case your review board has any questions for you.

Note to the apprentice: Please note that an important component of this project is demonstrating and practicing working with a client. You have a limited amount of time, and a fixed scope of work (as defined above)—this may require planning out your tasks, estimating how long those tasks will take, and negotiating with the clients about what certain requirements mean. It is suggested to document any verbal conversations in story cards, so that the rest of the review board can take a look.

Review Board

• The primary object objective of the review board is to answer the question: Is this person ready to join a client project as a Crafter?.
• The role of a review board member is to provide their own perspective working with or interacting with the apprentice over the course of the apprenticeship. Given their experiences, provide an answer to the question posed above.
• Since many of the review board members already had some interaction with the apprentice they are able to share any opinions and feedback ahead of the actual review board meeting via Lattice (as manager feedback), slack, email or in person with the Primary Mentor.
• If anyone on the review board is not able to attend the presentation, they may still share feedback to the primary mentor, as this feedback will be useful to the apprentice and the rest of the board.
• Feedback can be delivered directly to the apprentice, or can be given to the mentor to compile and deliver.
• The agenda on the day of the review board:
  • The apprentice will present and review board is able to ask any questions we have for them about the project.
  • The review board has a brief, high-level discussion about the code, presentation, and other artifacts from the capstone project.
  • The review board members have a chance to share anything else that hasn't yet been mentioned about the apprenticeship.
  • The review board has a chance to share their opinion about whether the apprentice is ready to be promoted as a Crafter on a specific client.