Ff system sdlc presentation_v0.6
Upcoming SlideShare
Loading in...5

Ff system sdlc presentation_v0.6






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • All Prototype teams will us UTi Agile methodology to produce Prototype Spec. When the team receives the Scopte they will breakdown the requirements to do determine the length of the effort. If the amount of time is estimated to take longer than 4 weeks the team will break down the effort in to multiple sprints.Each sprint will begin with Planning as described in Stage 3 Planning. The planning make take up to a week.Every day each team will start with a stand up where individually they describe what they did the previous day, what they are going to do the current day and if there are any impediments to completing their work.At the end of the day the effort remaining on any task is updated in RTC.At the end of every Sprint the Team will provide formal progress report including a demo to stakeholdersAt the end of every Sprint the Team will evaluate the previous Sprint to identify opportunities for improvements to be completed in the next Sprint.PMs and Leads will record stories/requirements and their associated tasks in RTC. The progress will be tracked daily.

Ff system sdlc presentation_v0.6 Ff system sdlc presentation_v0.6 Presentation Transcript

  • SDLC Presentation
    January 2011
  • Agenda
    End to end review of SDLC process
    Detail review of Prototype design stage
    Review prototype design stage deliverables list
    Additional SDLC documentation
  • Introduction
    Key features of SDLC
    UTi SDLC process is collection of Agile, Iterative, prototyping methodologies and best practices from HCL, Infosys.
    Uses Continuous Integration and Testing(Automated) methodologies that helps in identifying integration issues early.
    Uses Time boxing(Sprints) for early realization of high value features
    Helps with faster realization of prioritized requirements
    Uses parallel cross functional teams concept to achieve Time to Market goal for meeting the FF System Development timelines.
  • Introduction
    Items still need to be done as part of SDLC
    MDM(CIM tool) implementation approach for SDLC
    Need to expand on QA activities and engagement process with UST Global.
    Expand on Continuous Integration, Configuration management, Change management processes.
  • Introduction
    Key Success factors
    Team work with cross functional teams
    Identifying issues early
    Technical skills
    Working on right things; meeting deliverable expectations
    Stable technology platform, environments
    Continuous improvements
  • SDLC (Level 1)
  • Stage 1 – Foundation work
  • Stage 2 – Prototype team assignment
  • Stage 3 – Prototype Design
  • Stage 4 – SOW Sign off
  • Stage 5 – Development, QA
  • Stage 6 – Validation of Code
  • Stage 7 – Integration testing
  • Stage 8 – Quarterly UAT
  • Prototype design Stage
    Primary Objective within prototype stage is to elaborate requirements, produce detailed design artifacts that include outputs from tools like TIBCO Business Studio, Business works, Blaze etc. There will be some code skeletons produced as needed.
    Ready for offshore to code quickly.
    “Proof of concepts” are identified and conducted to reduce any architectural risks if necessary.
  • Prototype Stage 3 - Planning
  • Prototype Stage 3 - Execution
  • Sample representation of multiple tracks/streams
  • Prototype Team Methodology
    Prototype Teams will run with Agile like concepts
    Team determines how much time is needed – Sprint 2 to 4 weeks long
    Sprint planning at the start of each sprint – Stage 3 planning
    Daily stand ups – 15 minutes to see where we are at
    Daily task updates – primary way to track progress
    Sprint Reviews – Progress report and demo to stakeholders
    Sprint Retrospectives – Team reviews opportunities to improve
    All Stories and Tasks are tracked in RTC, daily report
  • Prototype Deliverables
    Prototype Specification
    Data Models – Logical, Physical and sample data
    Functional Model
    ARIS Model
    iRISE Model
    Business Studio Diagram/Link
    Function Work Steps
    Functional Data Elements
    Service Requirements
    Non-Functional Requirements
  • Additional Deliverables to Development
    Reference Architecture / Theory of Operations
    Solution Architecture
    Rules Catalogue
    Requirement Traceability Matrix
    Definition of Terms – EA Principles doc
    Global Style Sheet
    Global Error Message
    Global Navigation
    Common Services Reference
    User Interface Requirements & Guidelines
  • SDLC documentation
    Find SharePoint link SDLC in Home Page
    SDLC Process
    Prototype Specification, SOW template
    Deliverables from SDLC Stages and templates
    Roles and responsibilities(Product Owner, PM, Track Lead, BA, EA, Dev, QA, EIM, etc..)
    Product backlog Management process
    Sprint Planning, Retrospective, review documentation