1 / 29

Priit Salumaa Co-founder @Mooncascade Setting up & Delivering Your Project

Priit Salumaa Co-founder @Mooncascade Setting up & Delivering Your Project. Understand Yourself. Commitment. How much time you have during a week Don’t let your team-mates down Execution – the only thing that matters Keep your f*** word. Divide up Roles & Responsibilities. Project Manager

september-major
Télécharger la présentation

Priit Salumaa Co-founder @Mooncascade Setting up & Delivering Your Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Priit SalumaaCo-founder @MooncascadeSetting up & DeliveringYour Project

  2. Understand Yourself

  3. Commitment • How much time you have during a week • Don’t let your team-mates down • Execution – the only thing that matters • Keep your f*** word

  4. Divide up Roles & Responsibilities • Project Manager • Developers • Backend • Frontend • (Analyst?) • (Public face? / Client relations? / Sales Rep)

  5. Commitment Commitment is Über Important

  6. Learning • First, just try • 15min: Google • 20min: Ask • Google some more • Stack Overflow • Also: Github, maybe Quora

  7. Teaching & TeamPlay • Help others out • Pair Programming • Be a team player, don’t be a d*** • Have a beer together

  8. Understand Your Client

  9. Communication • Be pro-active • Be on the same page • Try to help, think along, be constructive • Manage expectations • If s*** hits the fan, communicate

  10. What does the Client Want • Analysis - an understanding with the client • Light vs Heavy analysis and documentation • Just some text vs tools and methodologies • Mockups vs a Prototype • Paper Prototyping (there’s an app for that), • Fluid UI, etc • Output: tasklist

  11. Plan with the Client • Make the client to prioritize • Divide the Project up into smaller pieces • Try to estimate the pieces • Work effort based on tasks • Calendar time • Create a plan (the initial plan always fails)

  12. What does the Client Want Communication is Über Important The understanding can change in time

  13. Set up Process

  14. Feedback from the Client • Client must be involved • Proactive communication • Make the client to review your work • Stay on the same page • Course correct

  15. Iterations • Repeating cycle • Work and feedback routine • Focus

  16. Choose Your Process • Processes by the book: RUP, XP, Scrum • By the book seldomly works • Example from Mooncascade • Weekly cycle – build, review, meeting • Daily cycle - PPP

  17. Personal Process • Everybody - Track your Time • Toggl • Developer - • Test your Code • Don’t commit broken code • Review (diff) other’s commits

  18. Personal Process - PM • Project manager – Feel the Pulse • Meetings – end with TODO’s and Commitments • Follow up the commitments • Communicate with the client • Adjust plans

  19. Set up Tools

  20. Communication Channel Create a Skype chat

  21. Code Repository • Teamwork implies Code Repository • CVS, SVN, Git, Mercurial, … • Choose Git :P • Run it your own or use a service • GitHub

  22. Task / Issue Tracker • Find a tool to • Distribute tasks • Track the progress • Visible to the client and the whole team

  23. A Simple Kanban Board Works

  24. Tracker Options • Google Drive • Github + HuBoard (free for OS only) • PivotalTracker – free for academic use • … just look for free stuff (Track, Bugzilla) • Or maybe your Client has one, or is willing to pay fortools (like Jira) :P

  25. Start the Project

  26. Kick-off • Start with a Kick-off meeting • Make sure the client understands the process • Divide tasks (volunteer basis) • Start the development cycle

  27. Process is not God • Modify the process during the project • Throw out practices which do not work • React to problems, find better practices

  28. Thank you

More Related