Single comment thread
See full discussion

hard to do a crash course in one post not knowing size of the team, schedule, methodology etc - but generally:

  • you need a priv repo to share code of course. With proper user/group permissions, on top of that sign proper paperwork with devs before giving them access to the repo (your new startup client will thank you later)

  • daily calls are good... but make them quick ones ie:

    • what a dev did yesterday
    • what is he/she going to do today
    • what blockages they face
  • weekly calls (Friday eve to close the week, Monday morning to plan) - are good if you need to react on changes

  • slack can be too distracting - especially for devs who need to stay in the flow

  • Trello / Asana - are good to plan and track work

  • depends on team size / schedule - you can try things like this weekdone.com/development-team…

  • Regarding project management - have a look at Kanban - and this video by Eric Brechner an Xbox development manager is gold www.youtube.com/watch?v=CKWvm…

  • mistakes? biggest f-ups happen when there is

    • lack of communication... when no one knows priorities and goals (short and long terms) - and do what THEY think is the most important
    • mess in code/documentation/project... - it's all good when there is 2 - 5 devs - but when you expect to get 20, 50 etc - some proper procedures need to be implemented
    • saying YES to too many things by lead developer / management (if something takes 3 weeks to develop and you promise to deliver it in 1 week - it's doable but there is some cost and Karma will get back to you in the future :P)
Home
Search
Messages
Notifications
More