| I didn't see this mentioned elsewhere but I would also start by getting a handle on all the outstanding tasks: If there are tickets, read and understand all the tickets, organize them in a way you can manage day-to-day. If you're working off some other spec, start breaking it up into individual tasks that can be managed on a spreadsheet or in a ticketing system. If you're working off general guidelines without documentation (and you can't run!), start by writing out all the tasks that need to be accomplished to finish the project. Even if they are brief. Now take the list of tasks and organize them into 2 "types" Stories: Tasks that deliver value to the end user Tasks: Tasks that are required or nice to have to enable 1 (Tasks or Chores) Now prioritize those into different buckets 1. MVP: if we don't ship this, the project will fail 2. Nice to Have: Someone _really_ wants this but it's not MVP 3. Phase 2 The more scope you can put into bucket 3 the more likely you'll be able to deliver _a_ working, functional project on time. You will get more credit for delivering something _good_ than failing to deliver the perfect project. Your team will also thank you for taking significant stress off their plate and for making them a success. |