Your SlideShare is downloading. ×
0
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Software Project Management for Entrepreneurs
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Software Project Management for Entrepreneurs

1,890

Published on

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,890
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
10
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Can use powerpoint,visio, etc
  • Transcript

    • 1. Managing Product Developmentfor Entrepreneurs<br />Wan Li Zhu<br />Fairhaven Capital<br />Blog: hacktrend.com<br />October 2011<br />1<br />
    • 2. My Background<br />Bachelors, Masters in Computer Science from MIT, HBS ’09<br />Most of my career @ Microsoft<br />Software engineering at SQL Server<br />Managed product development and later product marketing for Dynamics CRM (enterprise software)<br />Now VC @ Fairhaven Capital<br />2<br />
    • 3. Product Management<br />Product Development<br />Specifications<br />Architecture<br />Programming<br />Testing/QA<br />3<br />Product Marketing<br /><ul><li>Product positioning
    • 4. Marketing collateral
    • 5. Channel/sales
    • 6. Partnerships</li></ul>Engineering<br />Customer<br />
    • 7. Product Development Lifecycle<br />4<br />
    • 8. The Constraints of Software Projects<br />5<br />Choose 2 of the 3<br />Features<br />Speed<br />Quality<br />
    • 9. Waterfall vs. Lean – the oversimplified version<br />6<br />
    • 10. Waterfall vs. Lean – striking the right balance<br />Know what you’re building - coding is still hard and developer time is valuable (!)<br />Instead of writing long specs, aim for high level requirements and more wireframes<br />Prototype - test in small groups (alpha) to gather feedback and iterate<br />Managing bugs and quality pre-release is still important – have a triage process<br />Leverage existing software tools and platforms to launch your product quickly – don’t re-invent the wheel<br />Shift more towards a waterfall method when working with an outsourced development shop (more on this later…)<br />7<br />
    • 11. Roles in a Technology Organization<br />Starting out:<br />(CTO)<br />Developer<br />Outsourced UX<br />8<br />As the company grows:<br /><ul><li>CTO / VP Product / Architect
    • 12. Developer
    • 13. Designer (UX)
    • 14. Test (QA)
    • 15. Operations
    • 16. Biz-specific roles: User Education, Community Mgr</li></li></ul><li>What is a spec?<br />Wireframes – storyboards to quickly iterate on features and UI<br />Scenario – describes a user with a complex goal performing multiple actions (use cases)<br />Use case – a sequence of actions performed by a user that represent a “feature” in the software<br />Requirements – discrete must-haves that the product must meet<br />9<br />
    • 17. Spec Example: Facebook<br />Scenario: Joe is a college student and wants to stay on top of the latest happenings of his college friends. He first looks up his friends by their email address, then adds them, and once he’s connected checks regularly for their status updates.<br />Use cases<br />Add friends<br />Approve friend request<br />Monitor newsfeed<br />Comment on newsfeed item<br />Requirements<br />Must be able to look up people by email, by name, by school, etc.<br />Must be able to add friends (send invite to connect)<br />Must allow user to approve (or disapprove) of a request to friend<br />Must allow users to update their status with text, picture, location, etc<br />Newsfeed must be cached and updated on increments of X minutes<br />Etc etc<br />10<br />
    • 18. User Flow Diagram<br />11<br />Quick way to define user experience, get a sense of complexity<br />Forces you to flush out the product logic and flow<br />Can be created with MS Visio, Lucid Chart (online)<br />
    • 19. Storyboard (wireframe)<br />12<br />Keep it low-fidelity! Use for brainstorming, debating functionality, UI design iterations<br />Google<br />Search<br />2. Click search<br />1. Type in search term<br />
    • 20. Spec drives dev, test, marketing<br />13<br />Architecture / dev design<br />Time/effort estimates<br />Code + documentation<br />Dev<br />QA plan / test cases<br />Performance / scalability<br />Security<br />Spec<br />Test<br />Scenarios<br />Use cases<br />Features<br />Prioritization<br />UX wireframes<br />Product demo video<br />Product positioning<br />Marketing collateral<br />Support documentation<br />Marketing<br />
    • 21. Spec Best Practices<br />Stay organized: each scenario contains multiple use cases, each use case contains multiple requirements.<br />Prioritize (high, med, low) all scenarios, use cases, and requirements because it always takes longer than you think to implement features, and you will need to cut features to make deadlines. When cutting, important to keep track of dependencies.<br />Don’t forget requirements that are outside of explicit use cases, i.e. security, scalability. <br />Detailed specs are very helpful when it comes to managing outsourced development. Make sure code is well-documented, if possible ask for developer design docs also.<br />14<br />
    • 22. Bug curve<br />15<br />QA to a point, then release and fix/iterate. <br />SaaS/agile - release earlier and more often.<br />Enterprise – need a certain level of quality<br />Consumer – users can do some of the testing, fix rapidly<br /># of Bugs<br />Fix/iterate<br />Feature<br />Complete<br />Release<br />Time<br />
    • 23. Suggested Reading<br />16<br />

    ×