Daily Stand-up May 12, 2019

Sunday Retro: What did you accomplish this past week?

Janice @Janice

#weekly-retrospective, #daily-stand-up

The weekly retro gives hackers the space to:

  • Reflect on our triumphs for the week.
  • Reflect on where we fell short for the week.
  • Share concerns about being on track for your monthly epic and ask for feedback.

To join in:

01 Share your epic (a big chunk of work with a meaty objective) you'd like to complete by the end of May.

02 Share your triumphs for the week.

03 Share your failures for the week.

04 Share your concerns moving forward.

05 Give feedback to at least one fellow hacker and give them an IH Point for their check in.

Optional:

06 Share your Work In Progress to underscore your accomplishments.

(Smiling) The regular scheduled stand up will resume tomorrow.

  1. 4

    01 EPIC 🤔

    02 TRIUMPHS My triumph for the week is prepping for and recording 4 great podcast episodes, getting them all edited and writing all the copy, and inviting all the guests for my next podcast week. My first time doing that this year! (Okay, I haven't quite finished all this, but I'm 95% done and there's still time tonight.) This means I'll get to truly spend 3 weeks without doing anything for the podcast whatsoever. Just typing that sounds great.

    03 FAILURES I had to postpone this week's episode. First miss this year. But not the end of the world. I missed 5 episodes last year, and I don't think I'll miss any more this year since I'm finally on top of my backlog.

    04 CONCERNS I've got a lot of things I want to work on during this next 3-week sprint, and I'm worried about spreading myself too thin. But on the flip side, I'm worried about not getting enough promising initiatives out the door and moving too slowly. So I'm going to just go for it and see what happens. Ideally I can build one big thing per week.

    06 WIP The big things on the top of my mind right now are (in no particular order): some internal tools to fight spam, milestone leaderboard, bookmarking feature, our new articles system, and updates to the homepage's sorting algorithm.

  2. 1

    01 May EPIC — Make Three.do subscription-first

    Certain functionality must be finished before subscription model sounds sensible for my app and I can continue promoting it.

    02 Triumphs — Finally pushed out a huge feature update that I had been cooking for the last 2 months.

    03 Failures — the aforementioned update was originally planned to take 2 weeks.

    04 Concerns — I am lagging behind, and I’ve already let many opportunities slip. Perhaps that’s the moment when one would look for a co-founder. But I don’t have any people in my circles that would be eager to join AND whom I’d trust enough. All my biz/tech acquaintances are either already busy or not trustworthy.

    06 WIP: currently implementing cloud sync, which is a pillar of subscription-based offer. As usual, all WIP is on Twitter.

  3. 1

    May EPICS

    • [Magnus Rush] Automate podcast outbound emails based on user activity: 100% Complete

    • [Magnus Rush] Invite 30 podcasts to the platform: 7% Complete

    • [Announcr] Validate business interest with 10 survey responses/interviews: 4/10

    • [Announcr] Sign one customer for a paid pilot: 0/1

    • [Announcr] Prototype Consumer App for live demos: 45% Complete

    • [Announcr] Prototype Location Client App for live demos: 67% Complete

    TRIUMPS

    • [Magnus Rush] - Automated outbound emails which invite podcasts to the platform. I worked out a solution which isn't spammy, and doesn't email the podcast host more than once within 30 days. The email is based on a listener event, ie a listener started listening to the podcast using the MR mobile app, sends a tip, or leaves a voice message.

    I also got my first 2 monthly subscribers on the MR podcasting app, which felt incredible. The numbers are low, but relative conversion rate is a lot higher than what I expected. This is a false signal though, as it's not statistically significant yet.

    • [Announcr] Got a lot of the way through prototyping what I need to do a live demo of the Announcr solution. Some parts of it have been extremely challenging, and working through them gave me some fixes I could bring back over to MR. It felt really AWESOME to have found a new code pattern or two to add to my overall arsenal for the audio/voice space, where I seem to be spending a lot of time this year :)

    I also found an existing category of business solution which has some similarities to what Announcr is. This should make it easier to communicate what Announcr does in terms with something brick-and-mortar businesses are familiar with, or may use already.

    FAILURES

    Was a bit of a slow week due to immense day job hours. I get paid the same amount every month on this contract, so putting in the extra hours like that doesn't benefit me, and I'm getting pretty frustrated about it.

    CONCERNS

    One of the podcasts on the platform uses an audio format which I simply don't support yet. I haven't found a technical solution for it either, which is.. unusual for me. The awkward part of this is that the podcast is a podcast industry news podcast, and one which could be a strong advocate/ally for me going forward. I could convert and transcode all their files, but that is going to throw off stats for them. I'll dig around some more to see if there's something I'm missing this week.

    WIPs

  4. 1

    This comment was deleted 2 months ago.