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
SDLC Presentation<br />January 2011<br />
Agenda<br />Introduction<br />End to end review of SDLC process <br />Detail review of Prototype design stage<br />Review prototype design stage deliverables list <br />Additional SDLC documentation<br />
Introduction<br />Key features of SDLC <br />UTi SDLC process is collection of Agile, Iterative, prototyping methodologies and best practices from HCL, Infosys.<br />Uses Continuous Integration and Testing(Automated) methodologies that helps in identifying integration issues early.<br />Uses Time boxing(Sprints) for early realization of high value features<br />Helps with faster realization of prioritized requirements <br />Uses parallel cross functional teams concept to achieve Time to Market goal for meeting the FF System Development timelines.<br />
Introduction<br />Items still need to be done as part of SDLC<br />MDM(CIM tool) implementation approach for SDLC<br />Need to expand on QA activities and engagement process with UST Global.<br />Expand on Continuous Integration, Configuration management, Change management processes.<br />
Introduction<br />Key Success factors<br />Team work with cross functional teams<br />Identifying issues early <br />Pro-activeness<br />Technical skills <br />Working on right things; meeting deliverable expectations<br />Stable technology platform, environments<br />Continuous improvements<br />
Prototype design Stage<br />Objectives<br /> 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.<br /> Ready for offshore to code quickly.<br /> “Proof of concepts” are identified and conducted to reduce any architectural risks if necessary.<br />
Sample representation of multiple tracks/streams<br />
Prototype Team Methodology<br />Prototype Teams will run with Agile like concepts<br />Team determines how much time is needed – Sprint 2 to 4 weeks long<br />Sprint planning at the start of each sprint – Stage 3 planning<br />Daily stand ups – 15 minutes to see where we are at<br />Daily task updates – primary way to track progress<br />Sprint Reviews – Progress report and demo to stakeholders<br />Sprint Retrospectives – Team reviews opportunities to improve<br />All Stories and Tasks are tracked in RTC, daily report<br />
Prototype Deliverables<br />SOW<br />Prototype Specification<br />Data Models – Logical, Physical and sample data<br />Functional Model<br />ARIS Model<br />iRISE Model<br />Business Studio Diagram/Link<br />Function Work Steps<br />Functional Data Elements<br />Service Requirements<br />Routing/Entitlements<br />Notifications/Escalations<br />Non-Functional Requirements<br />
Additional Deliverables to Development<br />Reference Architecture / Theory of Operations<br />Solution Architecture<br />Glossary<br />Rules Catalogue<br />Requirement Traceability Matrix<br />Definition of Terms – EA Principles doc<br />Global Style Sheet<br />Global Error Message<br />Global Navigation<br />Common Services Reference<br />User Interface Requirements & Guidelines<br />
SDLC documentation<br />Find SharePoint link SDLC in Home Page <br />http://myuti.teams.go2uti.com/FreightForwarding/default.aspx<br />SDLC Process<br />Prototype Specification, SOW template<br />Deliverables from SDLC Stages and templates<br />RACI<br />Roles and responsibilities(Product Owner, PM, Track Lead, BA, EA, Dev, QA, EIM, etc..)<br />Product backlog Management process<br />Sprint Planning, Retrospective, review documentation<br />FAQ<br />
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.