Product Development

3,516 views

Published on

Product Development Best Practices

Agile vs. Waterfall

Development Processes and Documents

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

No Downloads
Views
Total views
3,516
On SlideShare
0
From Embeds
0
Number of Embeds
235
Actions
Shares
0
Downloads
1
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • 4/3/08 Stanford Continuing Studies: Bus100 - Building Software Products
  • Product Development

    1. 1. -Agile vs. Waterfall -Development Processes and Documents Product Development Best Practices JohnGibbon.com
    2. 2. Waterfall Agile Release Why
    3. 3. Agile versus Waterfall <ul><li>Waterfall / Traditional </li></ul><ul><li>Agile / Recent </li></ul><ul><li>Document, Feature, and Process Driven </li></ul><ul><li>Familiar and Understandable </li></ul><ul><li>Scalable: Distributed Teams & Junior Members </li></ul><ul><li>Long Term Goals Defined </li></ul><ul><li>No Throw Away Code </li></ul><ul><li>Better Suited for Mission Critical Deliverables </li></ul><ul><li>Less Death Marches </li></ul><ul><li>Demonstrable Intermediate Milestones; More Predictable Releases </li></ul><ul><li>Integration Testing Built-in </li></ul><ul><li>Flexible (Agile) During Development </li></ul><ul><li>More Realistic </li></ul><ul><li>Requires Trust, Negotiations, & Cooperation </li></ul>
    4. 4. (Usually) Agile Methodology Iterative and Incremental Development <ul><li>Short, Iterative Cycles (2-5 weeks) with Demonstrable Deliverables </li></ul><ul><ul><li>Plan, Requirements Analysis, Design, Code, Test, Document </li></ul></ul><ul><ul><li>At End, Should Have Releasable Software </li></ul></ul><ul><ul><li>Re-evaluate Priorities at End of Each Iteration </li></ul></ul><ul><li>Stories or Use-Case Based Development </li></ul><ul><ul><li> </li></ul></ul><ul><li>Time Driven, Not Feature Driven Development </li></ul><ul><ul><li>-Burn Down and Backlogs </li></ul></ul><ul><li>Scrums – daily face-to-face meetings </li></ul><ul><ul><li>-Pigs and Chickens </li></ul></ul><ul><li>Test Driven Development </li></ul>
    5. 5. Development Processes and Documents
    6. 6. What: Use Case Focused Product Requirements <ul><li>PRD (Product Requirements Document): </li></ul><ul><li>Uses Cases and More ! </li></ul><ul><ul><ul><li>Description of Actors or Users </li></ul></ul></ul><ul><ul><ul><li>Series of Use Cases: General to Specific </li></ul></ul></ul><ul><ul><ul><li>Non-Functional Product Requirements: Scalability, Security, Reliability, Availability, Installation, etc . </li></ul></ul></ul>Or Interactive Prototypes!
    7. 7. How: Technical Specifications <ul><li>Architecture Diagrams & Technical Specifications </li></ul><ul><ul><ul><li>Patterns </li></ul></ul></ul><ul><ul><ul><li>Standards </li></ul></ul></ul><ul><ul><ul><li>-Unit Tests - Test Driven Development </li></ul></ul></ul><ul><ul><ul><li>-Code Standards – Code Review </li></ul></ul></ul><ul><li>Test Plan </li></ul><ul><ul><ul><li>Integration and Use Case Test </li></ul></ul></ul><ul><ul><ul><li>Release Process and Document </li></ul></ul></ul>
    8. 8. Describe Overall Architectural Pattern Struts framework implementing MVC with Java Servlets and JSPs controller: struts controller servlet and action classes CONFIDENTIAL Page Especially to Create Rules for What Logic Lives Where
    9. 9. Describing a New Architectural Pattern CONFIDENTIAL Page Architectural Next Steps: transform XML to HTML via XSLT (Collaboration Diagram: Object View with Numbered Sequences)
    10. 10. Architecture Overview Page J2EE Foundation Application Services Search J2EE Application Server Reporting Workflow Forms Security Auditing Doc Mgmt Messaging Enterprise User Remend Manager <ul><li>Inbox </li></ul><ul><li>File Cabinet </li></ul><ul><li>Reports </li></ul><ul><li>Contacts </li></ul><ul><li>Config & Admin </li></ul>Vendor Vendor Workspace <ul><li>Inbox </li></ul><ul><li>Tasks </li></ul><ul><li>Actions </li></ul><ul><li>Reports </li></ul>-- Workflow, Forms, Reports -- Domain REO Foreclosure Loss Mit Asset Eval <ul><li>Occupancy </li></ul><ul><li>Cash4Keys </li></ul><ul><li>Eviction </li></ul>••• <ul><li>Title </li></ul><ul><li>Legal </li></ul><ul><li>HUD </li></ul>••• <ul><li>Process </li></ul><ul><li>Audit </li></ul><ul><li>Approval </li></ul>••• <ul><li>Counseling </li></ul><ul><li>Workout </li></ul><ul><li>Refinance </li></ul>••• Legacy Data <ul><li>RDBMS </li></ul><ul><li>Doc Mgmt </li></ul><ul><li>Proprietary DB </li></ul><ul><li>Servicing </li></ul>Integration Modules Data API Document
    11. 11. Overall Service Topology

    ×