1
4 Comments

Looking for product/project management help!

I've been coding for about 2 years now, and after building out a number of smaller apps (Rails/Node/React/etc.) I'm going to start building out my first SAAS app for paying customers.

I'm considering building out a small team to help me launch the MVP (a designer and a senior backend developer.)

I have pages of project specs that I'm trying to figure out how to split up into workable milestones. Additionally, I've never used anything other than Github issues to manage a software project.

Can anyone recommend books/blogs/online courses/etc. to manage a project with 2-3 members? Does anyone here offer consulting/coaching for this type of thing?

on July 17, 2019
  1. 1

    What have you done to validate your business model?

    1. 1

      Good question-- I'm working with someone (non technical) who has domain expertise, and there are already a number of products in the space. We think we have a few differentiators and competitive advantages, but we're not launching a new category by any means.

  2. 1

    As a fellow developer who's had similar problems I can give you my prospective and what worked for me.

    First off, it takes time, the more projects your work on the easier it gets to start thinking about them in terms of tasks/stories/whatever. It also gets easier to make estimations for things like time and level of effort which further helps with planning.

    In terms of strategies I like to think about things in terms of components. I do a lot of work with React, so its what makes sense to me; I think about what my UI components are going to be and those end up being tasks. I then have additional tasks for the backend stuff that wires it up. I do full stack, but like to think about them as two separate streams of work to keep things organized.

    I've always been a big fan of trello and Kanban boards, especially on small teams. Matching up my tasks with card, and then dragging them across the board gives me a good sense of progress and let's everyone know what's still on the list. It's also not too much overhead to quickly create cards, some software I've found to take up way too much of time. I'd prefer something quick and simple for a smaller team.

    Another big thing I struggled with was making my tasks too big. I'd always err on side of caution and rather have too many tasks than too few. This is especially the case for more formal settings with things like code reviews where you're not trying to take in too much at once. It also helps with things like testing and catching bugs too as you're not trying to juggle too much functionality at once.

    This is sort of a loose answer, but I think project planning can be a bit a fluid. Try to think about components, break it up into small pieces, but don't be afraid to bend and break the plan. I'm also not a master planner by any means, but I've delivered multiple projects on time so I like to think I know at least a little bit.

    1. 1

      Thanks for the detailed response. Thinking in terms of React components is definitely a smart way of breaking up tasks. I'll also look into Trello, and see if that works better than Github issues.