1 / 16

TECH 50800 Project A Look at Software Development Champion/Define Phase

TECH 50800 Project A Look at Software Development Champion/Define Phase. Date: 10/02/2013 Team members: Travis W. Gillison. Project Charter Details . Business Case Problem Statement Project Scope/Goal Statement Deliverables Stakeholders SIPOC SWOT CTQ ROI. Business Case.

melina
Download Presentation

TECH 50800 Project A Look at Software Development Champion/Define Phase

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TECH 50800 ProjectA Look at Software DevelopmentChampion/Define Phase Date: 10/02/2013 Team members: Travis W. Gillison

  2. Project Charter Details • Business Case • Problem Statement • Project Scope/Goal Statement • Deliverables • Stakeholders • SIPOC • SWOT • CTQ • ROI

  3. Business Case Customers are billed per hour of development time. Projects are taking too long to develop from requirements to software delivery, and customers are beginning to rescind offers and go to competitors. Quite simply, it’s taking too long for the projects to get implemented. This needs to change.

  4. Problem Statement The process of delivering the software has become overly convoluted, and it takes too long from the time that an RFP (Request for Proposal) is sent for a potential bid, to a contract win and subsequent execution. Customers are buying high stakes deliverables, and require excellent service. The length of time for the projects to complete has caused customers to delay their own business processes and we have been inefficient with our own resources. Key Points: • Long development times • Long quality assurance times • Higher billables; higher costs for customers • Implementations are delayed

  5. Project Scope/Goal Statement • The Lean Six Sigma process will be used to identify areas of waste and inefficiencies in the requirements-to-deliverable software process. All areas of the process will be analyzed, to help quantify some of the areas that are needlessly delayed. On average, projects take 6 to 9 months to complete. The goal is to reduce the time of completion by 25%.

  6. Deliverables • Reduce development time, therefore reducing billable hours to our customers • Decrease quality assurance time without sacrificing defect control • Error-free documentation with clear, concise instructions • Proper training/hand-offs to support and technical resellers

  7. Stakeholders

  8. SIPOC Outputs Suppliers Inputs Customers Process Development Process (code creation) Test Case creation and execution (Quality Assurance) Documentation Sales Demo Support/Engineering Hand off Localization (if necessary) Implementation Product Managers Developers Sales Engineers Testers Development Plan Architecture/ UML diagrams Requirements documents Sales contract Topologies Software package CD-ROM, DVD or DLC Hardware (if required) Technical/ Administration Guides Customer training Contact Centers Resellers Support

  9. Stakeholder Analysis

  10. SWOT Analysis Strengths • Resource pool is large(SMEs) • Desire to increase service for our customers found at all levels • Can respond quickly to changing customer needs

  11. SWOT Analysis (continued) Weaknesses • Scope of project can change rapidly • Requirements are often misunderstood or omitted • Communication across teams gets convoluted • Code completion/QA testing can exceed desired timeframes

  12. SWOT Analysis (continued) Opportunities • Gain valuable metrics on actual development and QA time • Increase communication, particularly with pre-implementation staff (sales, sales engineers) • Higher quality deliverables • Faster delivery

  13. SWOT Analysis (continued) Threats • Customer changes increase scope and increase delivery time which could jeopardize entire project and give up business to competitor • Poor communication across teams could lead to finger pointing at project completion

  14. CTQ Tree

  15. ROI • The amount of ROI potential varies greatly due to the extremely volatile market of customer needs. Customers are billed for development time in “chunks” (for example, a 40 hour chunk billed at $300/hour would be $12k). The amount of customizations change the dev hourly requirements • Less call flows into support allows less dev time spent on fixing defects which will raise profitability and productivity

  16. ROI (continued) • Faster deliverables increases chances of repeat business • Sales staff will get paid commissions quicker due to faster implementations

More Related