33rdrd Class Class

-Business Cases – Value Proposition-Business Cases – Value Proposition

-Product Development and Product -Product Development and Product Requirements Best PracticesRequirements Best Practices

Bus100: Building Software Bus100: Building Software Products:Products:From Strategy to SalesFrom Strategy to Sales

John GibbonJohn Gibbon

•DefineDefine

•Design Design

•Develop Develop

•PartnerPartner

•MarketMarket

•Sell Sell

1-3: Company & Product Strategy1-3: Company & Product Strategy

3: Development & Requirements 3: Development & Requirements 4: Product Management4: Product Management5: User Experience5: User Experience6: Web Tech, QA, Teams 6: Web Tech, QA, Teams 7: Project Management7: Project Management 7: Partnering7: Partnering 8: Product Marketing8: Product Marketing 9: Sales & Advertising 9: Sales & Advertising 10: Mistakes / Review 10: Mistakes / Review

Classes:Classes:

Your Value PropositionYour Value Proposition

Impediments to Sustaining Impediments to Sustaining ValueValue

Hal Louchheim Hal Louchheim

Sustaining Value IdeasSustaining Value Ideas

Using “Built to Last” concepts

Product Development and Product Product Development and Product Requirements Best Practices Requirements Best Practices -Agile vs. Waterfall -Agile vs. Waterfall -Requirements Writing -Requirements Writing -Other Dev Processes and Docs -Other Dev Processes and Docs

Bus100: Building Software Bus100: Building Software Products:Products:From Strategy to SalesFrom Strategy to Sales

John GibbonJohn Gibbon

Manifesto for Agile Software Manifesto for Agile Software DevelopmentDevelopment

We are uncovering better ways of developingsoftware 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 onthe right, we value the items on the left more.

AgileManifesto.org (2001)

(Usually) Agile Methodology(Usually) Agile MethodologyIterative and Incremental DevelopmentIterative and Incremental Development

1. Short, Iterative Cycles (2-5 weeks) with Demonstrable Deliverables1. Plan, Requirements Analysis, Design, Code, Test,

Document2. At End, Should Have Releasable (or Demonstrable)

Software3. 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

Posted in Scrum Meeting RoomPosted in Scrum Meeting RoomWhat Report During Scrum?What Report During Scrum? Project PrinciplesProject Principles

• Accomplishments since last Accomplishments since last Scrum Scrum

• Accomplishments before next Accomplishments before next ScrumScrum

• Future roadblocks and risksFuture roadblocks and risks

• Decided/learned anything new Decided/learned anything new should share with teamshould share with team

• Discussion outside Scrum Discussion outside Scrum required?required?

• Changes required in task Changes required in task schedule? schedule?

• Customer FocusedCustomer Focused• Continuous ImprovementContinuous Improvement• Best Practices Based on Best Practices Based on

Agile/ScrumAgile/Scrum• Time boxed, “Sprints”, Time boxed, “Sprints”,

simplicity, communication, simplicity, communication, support/empower team and support/empower team and individualindividual

• Agile Manifesto: Agile Manifesto: -Individuals and -Individuals and interactions over processes interactions over processes and toolsand tools -Working software over -Working software over comprehensive comprehensive documentationdocumentation

Release

Why

WaterfallWaterfall

AgileAgile

Agile versus WaterfallAgile versus Waterfall

Waterfall / TraditionalWaterfall / TraditionalAgile / RecentAgile / Recent

• Document, Feature, and Document, Feature, and Process DrivenProcess Driven

• Familiar and Familiar and UnderstandableUnderstandable

• Scalable: Distributed Scalable: Distributed Teams & Junior MembersTeams & Junior Members

• Long Term Goals DefinedLong Term Goals Defined• No Throw Away CodeNo Throw Away Code• Better Suited for Mission Better Suited for Mission

Critical Deliverables Critical Deliverables

• Less Death MarchesLess Death Marches• Demonstrable Demonstrable

Intermediate Milestones; Intermediate Milestones; More Predictable ReleasesMore Predictable Releases

• Integration Testing Built-Integration Testing Built-inin

• Flexible (Agile) During Flexible (Agile) During DevelopmentDevelopment

• More RealisticMore Realistic• Requires Trust, Requires Trust,

Negotiations, & Negotiations, & CooperationCooperation

Requirements: PersonasRequirements: 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

Use Case Diagram: Use Case Diagram: Functional Requirements Functional Requirements Describing System from User Describing System from User Perspective Perspective

13

member

Photo Sharing Site

upload

organize

view

friend administrator

Requirements DocumentationRequirements Documentation

Member

Photo Site

UploadPhotoUploadPhoto

Share?

Shares Photo w/ Group

UML Activity (Use Case) DiagramUML Activity (Use Case) Diagram

UML (Unified Modeling Language) provides a variety of UML (Unified Modeling Language) provides a variety of different diagram types to describe a software system: different diagram types to describe a software system: activity diagram, collaboration diagrams, etc. activity diagram, collaboration diagrams, etc.

UML Activity (Use Case) DiagramUML Activity (Use Case) Diagram

Use Case Functional Requirements Use Case Functional Requirements DocumentationDocumentation

1. Use Case Name2. Goal / Summary3. Actors4. Preconditions5. Triggers6. Basic Course of Events7. Alternative Paths8. Postconditions9. Business rules

Requirements: High Fidelity Requirements: High Fidelity PrototypesPrototypes

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

Prototypes ToolsPrototypes 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

Other Development Processes and Other Development Processes and DocumentsDocuments

Other Development Processes and Other Development Processes and DocumentsDocuments

Other Development Processes and Other Development Processes and DocumentsDocuments

Other Development Processes and Other Development Processes and DocumentsDocuments

CONFIDENTIAL

Page 23

Describe Overall Architectural PatternDescribe Overall Architectural PatternStruts framework implementing MVC with Java Servlets and JSPs Struts framework implementing MVC with Java Servlets and JSPs controller: struts controller servlet and action classescontroller: struts controller servlet and action classes

Especially to Create Rules for What Logic Lives Especially to Create Rules for What Logic Lives WhereWhere

CONFIDENTIAL

Page 24

Describing a New Architectural Describing a New Architectural PatternPattern

Architectural Next Steps: Architectural Next Steps: transform XML to HTML via XSLTtransform XML to HTML via XSLT

(Collaboration Diagram: Object View with Numbered (Collaboration Diagram: Object View with Numbered Sequences) Sequences)

Page 25

Architecture OverviewArchitecture OverviewEnterprise User

RemendManager

•Inbox

•File Cabinet

•Reports

•Contacts

•Config & Admin

Vendor

VendorWorkspace

•Inbox

•Tasks

•Actions

•Reports J2EE Foundation

Ap

pli

cati

on

Serv

ices

Search

J2EE Application Server

Reporting

Workflow

Forms

Security AuditingDoc Mgmt

Messaging

-- Workflow, Forms, Reports --

Dom

ain

REOForeclosure

Loss MitAsset Eval

•Occupancy•Cash4Keys•Eviction•

••

•Title•Legal•HUD••

•

•Process•Audit•Approval•

••

•Counseling•Workout•Refinance•

••

Legacy

Data

•RDBMS

•Doc Mgmt

•Proprietary DB

•Servicing

Inte

gra

tion

Mod

ule

sD

ata

AP

I

Document