|
So I take my SEO strategy, which I’ve probably worked on for months, agonized and perfected, and I pull out all the tasks I think a particular team will do. Then I take that and do a rough grooming and sizing session for those tasks with someone who knows what they’re talking about – usually, with the product owner of that squad. And if you don’t know who that is, it’s a good time to make friends. I swear, 90% of being an.
Note: Depending on your organization, your team might estimate DB to Data differently. Sometimes, it’s in days. Other times, it’s using an agile Fibonacci scale or something similar. Whatever it is, you’ll want to be consistent. A Fibonacci scale can make translating to days in order to estimate the time frame a bit more difficult. Still, I’d lean on the team to give an average execution time so you can then put in at least an estimated delivery.
This estimation process is helpful for enterprise-level companies because, assuming the conversation goes well, you’re essentially getting a soft yes from that team. That’ll make it easier for them to say yes for real when the work comes across their desk later. And then once that’s done, for me, it’s mostly paperwork. 3. Do the paperwork For me, there’s no better format than Gantt when it comes to timed work and keeping track of it. You can build it like I typically do in Google Sheets or use software-based versions in tools like Jira or Monday.
|
|