1. 3 rd Class -Business Cases – Value Proposition -Product Development and Product Requirements Best Practices Bus100: Building Software Products: From Strategy to Sales John Gibbon

2. DefineDefine DesignDesign DevelopDevelop PartnerPartner MarketMarket SellSell 1-3: Company & Product Strategy 3: Development & Requirements 4: Product Management 5: User Experience 6: Web Tech, QA, Teams 7: Project Management 7: Partnering 8: Product Marketing 9: Sales & Advertising 10: Mistakes / Review Classes: Classes:

3. Your Value Proposition For Target Customer Who Problem / Pain ( “must have” not “nice to have”) The Product Name / Product Category That Solution / Key Problem Solving Capability Unlike Competitors / Alternatives Our Product Key Differentiators / Product Features

4. Impediments to Sustaining Value Customers or their needs changeCompetition catches up or “leapfrogs”New entrants into the spaceMarket “saturation”Market environment changesCompany performance issues Hal Louchheim

5. Sustaining Value Ideas Build true marketing capability, not just a single productFocus on customers, not solely profits Strengthen the relationship through full communication and branding Preserve the core; stimulate progress: seek both increment improvements AND breakthrough advances Culture counts: Values, Vision, BHAG, Clock Builders Stay with one’s core strengths; but go for total quality in every aspect Using “Built to Last” concepts

6. Product Development and Product Requirements Best Practices -Agile vs. Waterfall -Requirements Writing -Other Dev Processes and Docs Bus100: Building Software Products: From Strategy to Sales John Gibbon

7. 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. AgileManifesto.org (2001)

8. (Usually) Agile Methodology Iterative and Incremental Development 1.Short, Iterative Cycles (2-5 weeks) with Demonstrable Deliverables 1.Plan, Requirements Analysis, Design, Code, Test, Document 2.At End, Should Have Releasable (or Demonstrable) Software 3.Re-evaluate Priorities and Process at End of Each Iteration 1.Use-Case or Story Based Development -Stories Shorter, Fit within Iteration 2.Time Driven, Not Feature Driven Development -Burn Down and Backlogs 3.Scrums – daily face-to-face meetings -Pigs and Chickens 4.Test Driven Development

9. Posted in Scrum Meeting Room What Report During Scrum? Project Principles Accomplishments since last ScrumAccomplishments since last Scrum Accomplishments before next ScrumAccomplishments before next Scrum Future roadblocks and risksFuture roadblocks and risks Decided/learned anything new should share with teamDecided/learned anything new should share with team Discussion outside Scrum required?Discussion outside Scrum required? Changes required in task schedule?Changes required in task schedule? Customer FocusedCustomer Focused Continuous ImprovementContinuous Improvement Best Practices Based on Agile/ScrumBest Practices Based on Agile/Scrum Time boxed, “Sprints”, simplicity, communication, support/empower team and individualTime boxed, “Sprints”, simplicity, communication, support/empower team and individual Agile Manifesto: -Individuals and interactions over processes and tools -Working software over comprehensive documentationAgile Manifesto: -Individuals and interactions over processes and tools -Working software over comprehensive documentation

10. DesignDevelopTestDefine WhyDefineDesignDevelopTestRelease Why Waterfall Agile

11. Agile versus Waterfall Waterfall / Traditional Agile / Recent Document, Feature, and Process DrivenDocument, Feature, and Process Driven Familiar and UnderstandableFamiliar and Understandable Scalable: Distributed Teams & Junior MembersScalable: Distributed Teams & Junior Members Long Term Goals DefinedLong Term Goals Defined No Throw Away CodeNo Throw Away Code Better Suited for Mission Critical DeliverablesBetter Suited for Mission Critical Deliverables Less Death MarchesLess Death Marches Demonstrable Intermediate Milestones; More Predictable ReleasesDemonstrable Intermediate Milestones; More Predictable Releases Integration Testing Built-inIntegration Testing Built-in Flexible (Agile) During DevelopmentFlexible (Agile) During Development More RealisticMore Realistic Requires Trust, Negotiations, & CooperationRequires Trust, Negotiations, & Cooperation

12. Requirements: Personas 1.Alan Cooper “Inmates Running the Asylum” 2.Example of Actor (“CFO” “Educated Mom”) - Their Goals, Capabilities, Context 3.Leads to User Centered Not Self Referential Design 4.Examples 5.Discuss in Product Discovery and Product Design

13. Use Case Diagram: Functional Requirements Describing System from User Perspective 13 member Photo Sharing Site upload organize view friendadministrator Requirements Documentation

14. Member Photo Site Upload Photo Upload Photo Share? Shares Photo w/ Group UML Activity (Use Case) Diagram UML (Unified Modeling Language) provides a variety of different diagram types to describe a software system: activity diagram, collaboration diagrams, etc.

15. UML Activity (Use Case) Diagram

16. Use Case Functional Requirements Documentation 1. Use Case Name 2. Goal / Summary 3. Actors 4. Preconditions 5. Triggers 6. Basic Course of Events 7. Alternative Paths 8. Postconditions 9. Business rules

17. Requirements: High Fidelity Prototypes 1.Discussed by Marty Cagan 2.Realistic Enough to Test Idea with Target Customer 3.Refine Business Idea Before Commit 4.Helps Product Be Better Understood Throughout Org 5.Underlines Functionality and User Experience Intertwined 6.Will Be Further Discussed - Marty – Product Discovery - Glen – Product Design

18. Prototypes Tools 1.Lower Fidelity -PowerPoint / Visio (Storyboarding) 1.HTML Development Tools: - Weebly, Google Sites, SquareSpace (free, drag and drop) - Dreamweaver, FrontPage (not free, web authoring tools) 2.Code Development Tool -VisualBasic, etc. 3.High Fidelity Prototyping Tools: - Axure and Irise - Also Serena Composer, Lucid Spec, Intuitect, Profesy

19. Other Development Processes and Documents

23. CONFIDENTIALPage 23 Describe Overall Architectural Pattern Struts framework implementing MVC with Java Servlets and JSPs controller: struts controller servlet and action classes Especially to Create Rules for What Logic Lives Where

24. CONFIDENTIALPage 24 Describing a New Architectural Pattern Architectural Next Steps: transform XML to HTML via XSLT (Collaboration Diagram: Object View with Numbered Sequences)

25. Page 25 Architecture Overview Enterprise User Remend Manager Inbox File Cabinet Reports Contact s Config & Admin Vendor Vendor Workspace Inbox Tasks Actions Reports J2EE Foundation Application Services Search J2EE Application Server ReportingWorkflowForms SecurityAuditing Doc Mgmt Messaging -- Workflow, Forms, Reports -- Domain REO Foreclosur e Loss MitAsset Eval Occupancy Cash4Keys Eviction Title Legal HUD Process Audit Approval Counseling Workout Refinance Legacy Data RDBMS Doc Mgmt Proprietary DB Servicing Integration Modules Data API Document