Toggl | Intake Approach

Autoplay
Autocomplete

Previous Lesson Complete and Continue

RDOS Team Member Onboarding

Non-disclosure

Everything is under NDA unless otherwise stated in writing (1:34)

Information needed

Contract (0:44)
Bitbucket username (0:44)

Tools

Slack (1:07)
JIRA (0:41)
Toggl (1:04)
Bitbucket (0:51)
Google Drive/Docs (0:53)
Google email account (0:57)
Lastpass (1:53)
Two-factor Authentication (1:25)
Quickforget.com (3:10)

Workflow

JIRA Workflow (11:14)
Tickets stay assigned to the primary developer (3:37)
Remember the point scale: 1 - 15m, 1.5 - 45m, 2 - 1.5h, 3 - 4h, 5 - 7h, 8 - 1.5d, 13 - 1wk (2:56)
If you do make a ticket, the ticket summary should be super simple to understand - just 5-7 words. (1:52)

Concepts to know

The entire development cycle overview (6:55)
Pareto Principle (80/20 Rule) (8:14)
Parkinson's Law (3:12)
Swiss Cheese (5:01)
How tickets are broken up and why (4:49)

Deal-breakers

All tickets need to be in the current status in JIRA (1:07)
Direct message Casey if you’re not getting the results you need from the team (2:24)
Queue enough work to have several days of tasks loaded up (2:03)
Which tickets to track your time to (7:02)
Don't work for free. Track all your time to a ticket. (2:36)
Use the daily prioritization project (2:23)
Try really hard to not exceed the estimate on the ticket (4:14)
The time you invoice us for must match what's tracked in Toggl (2:35)
Track your time in real time (2:57)
Toggl time entries should have a ticket prefix (1:14)
Daily scrum (1:42)

Teach online with

Toggl

Lesson content locked

If you're already enrolled, you'll need to login.

Enroll in Course to Unlock