Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

The 5 things you need to know to start a software project

The 5 things you need to know to start a software project

Herunterladen, um offline zu lesen

Before you hire developers, before you start your next app project, there are some things you can do to make your project more successful from day one.

Before you hire developers, before you start your next app project, there are some things you can do to make your project more successful from day one.

Weitere Verwandte Inhalte

Ähnliche Bücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

Ähnliche Hörbücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

The 5 things you need to know to start a software project

  1. 1. The 5 Things You Need to Know to Start a Software Project Jason Straughan - Grok Interactive / Codeup
  2. 2. Why?
  3. 3. All Software Starts with A PROBLEM
  4. 4. What’s the Problem? ● Define the Problem ● Explore Status Quo ● Study Competition ● Discover Alternatives
  5. 5. MVP It’s all about that
  6. 6. You’ve Got 99 Features Pick Three!
  7. 7. “It’s tough to make predictions, especially about the future.” - Yogi Berra
  8. 8. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  9. 9. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  10. 10. Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas Manifesto for Agile Software Development
  11. 11. Domain Driven Design
  12. 12. “To communicate effectively, the code must be based on the same language used to write the requirements—the same language that the developers speak with each other and with domain experts.” Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software
  13. 13. if X is in Y then multiply A by B
  14. 14. if ZIP CODE is in THIS STATE then multiply the SHOPPING CART TOTAL by SALES TAX
  15. 15. Project Management
  16. 16. User Stories As a USER TYPE when I DO SOMETHING I want OUTCOME.
  17. 17. User Stories As a signed in, registered user when I click on the map icon in the navigation bar I want to see available drivers in my area on a map centered on my current location.
  18. 18. Communication Protocols ● Stakeholders ● Project Managers ● Developers ● Other Team Members
  19. 19. You Say Bug, I Say Feature Let’s Call the Whole Thing Off
  20. 20. TDD Test All the Things
  21. 21. Code Reviews Are Fair and Balanced
  22. 22. Jason D. Straughan @jdstraughan jasons@grok-interactive.com Josh Freeman @joshfreemanIO josh.freeman@grok-interactive.com @GrokInteractive

Hinweis der Redaktion

  • Developers are expensive!

×