Roles & Responsibilities Web Product Development Works integrally with the dotcom development team through iterations

s of sprints to validate and provide upfront feedback on UI/design/functionality IA Analyst\Manager - designs and creates the Information Architecture document (Wireframes) Comp Analyst\Manager - designs and creates the visual designs (Mockups) Producer Analyst\Manager - comes up with ATG Message Keys, Targeters, Fields Creative Team - creates the content & assets (Images, Videos, etc...) IT

Works jointly with the web product developmetn team to facilate high quality deliverables Scrum Master\Project Manager facilitates meetings capture meeting notes communicates status to team, product owners, stakeholders and upper management project schedule timeline budget status reports risk management change management works with resource manager for LOEs and ETC works with product owner on upcoming iniatiatives

works with ITAM works with other Enterprise groups resolve impediments Business Analysis - writes the IA, SAS, and COR ESD Analysis - creates the high-level conceptual design and HLD Systems Analysis - writes the User Stories, FRD, Mini-Spec, clarifies business rules

Dev Lead - design, develope, unit test, code reviews, oversees and guides the development team Development Team - develope, unit test, documentation DevTest - test plan, test strategy, test cases, test execution, log defects SQA Lead - test plan, test strategy, test cases, test execution, log defects SQA Analyst - either onshore or offshore, this person will support the SQA lead, automation test, performance test Artifacts Product Backlog - a high-level document for the entire project. It contains backlog items: broad descriptions of all required features, wish-list items, etc. prioritized by business value. It is the 'What' that will be built. Sprint Backlog - a document containing information about how the team is going to implement the features for the upcoming sprint. Features are broken down into tasks. Burndown Chart - publicly displayed chart showing remaining work in the sprint backlog. Updated every day, it gives a simple view of the sprint progress.

Meetings
There are 3 main meetings in scrum: Daily Standup - meeting is timeboxed to 15 minutes, at the same location and same time every day, addresses 3 things: (1) What did I do yesterday (2) What am I going to do today (3) Impediments I have that's preventing me from working. Sprint Planning\Review - at the beginning of the sprint cycle (every 7 to 30 days), selects and identifies what work is likely to be done during the current sprint. Review the work that was completed and not completed and demos the completed work. Retrospective Meeting - reflect on past sprint, strive to make continuous process improvements, 2 main questions: (1) What went well during the sprint? (2) What could be improved in the next sprint? Timeboxed to 3 hour time limit. As a rule of thumb, keep the format the same. The meeting should be about accomplishments and an open forum to allow for feedback and should be non-confrontational.

Food/Pizza! Agenda Ice Breaker - Play a Video A quick look back of what we've accomplished Action Items from the previous retrospective

Round Robing - group activity where everyone has the opportunity to provide feedback (on things that went well, things can be improved upon, any action items) Recap - Action Items & Take Aways Below are a few examples: (make sure you click on the ppt)

These are periferial meetings: Scrum of Scrum - occurs each day normally after the daily scrum. Allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration. A designated person from each team attends. Communication There are several ways we communicate to the project team and stakeholders We use a Distribution list (ie: Adapt Team, Edapt Team, IT BAU Scrum Team) We hold daily stand ups We provide a weekly status report to all our stakeholders We hold weekly planning sessions We send out meeting notes after each meeting We send a slide to Enterprise Release Management when project turns yellow/red to explain why and steps to green We post all documentation on the wiki Tools We use several tools during the system development life-cycle. These are typically industry standard tools that we use here at Directv.com Stories & Requirements - MSWord Project Management - ePlan (Clarity), Visio, Wiki Resource Management - ePlan

Budget - IT Project Budget Template

Sprint Burndown & Task Tracking - Custom Excel, ScrumWorks (POC), Jira/Greenhopper (POC) Content Management - ATG (For Content, Message Keys, Targeters) Content Delivery Network (CDN) - LimeLight Release Management - Release Information Document(RID) Code Merge & Version Control - Subversion Defect Tracking - HP Test Director Performance Test - HP Quick Test Pro Browser Compatibility Testing - Gomez

Documentation We post all of our documentation whether from IT or Product Development on our Wiki. The Product Development team has an entire suite of tools called ActiveCollaboration and FileManager they use. However, once document is complete, it's shared on our wiki. Below are documents produced by any scrum team. Project Management Communication Plan Assumptions/ Issues / Risks / Action Item Registry Annual Overview Calendar - depicts major releases for the entire year

Project Timeline Chart - scrum pipe chart with major milestones and dependencies (Project Plan equivalent) Burn-down Chart - hours completed vs. hours remaining for each sprint Status Reports Meeting Notes

Team Contact List Product Development Deliverables Product/Sprint Backlog Information Architecture (IA) & Wireframes - concepts Visual Designs - comps Producer Documentation - ATG message keys, targeters, legal text Reporting - Omniture Reporting Requirements for tagging Online Marketing Emails - Merkle(3rd party vendor) Email HTMLs Business Analysis/Systems Analyst User Stories - contains high level major feature and acceptance criteria of complete Sprint Matrix - list of major components/ user stories in each sprint & scope

Functional Requirements Document (FRD) - contains Business Rules, Flows, Interactions, Use Cases Development Detailed Design - contains High Level Design (HLD equivalent, Class Diagram, Sequence Diagram, Data Model, PCI Compliance) High Level Task Breakdown - work breakdown of user stories into chunkable, workable parts for development Detailed Task Breakdown - individual functionality task cards with developer responsible, task, and number of hours associated to the task Testing Test Strategy Test Plans Test Cases Test Scripts (Automation)

Test Scripts (Performance) Defect List Defect Status Report Demo User Acceptance User Acceptance Test Plan User Feedback User Approvals