Download - Applied Technology Institute

Agile In The Government Environment# A112Agile Collaborating & CommunicatingAgile Requirements # A124There are many dates and locations as these are popular courses: See all at:www.aticourses.com/Agile_Courses_Schedule.htmlNovember 12-14, 2014Live VirtualNovember 20-21, 2014Washington, DC$1395 (Live 8:00am - 6:00pm)(Virtual, noon – 6:00 pm)"Register 3 or More & Receive $200 00 eachOff The Course Tuition."SummarySoftware procurement and development efforts arenow required by the Federal Government to increasetheir efficiency and effectiveness. For that reasonmany government agencies and their contractors aremoving toward the Agile approach in the developmentand delivery of their software and other services. Inorder to transition to Agile methods within thegovernment’s already in place procedures you need toknow how to convert your procedures.This 2-day (3-day virtual) class delivers the bridgebetween what Agile is and how to effectively use it inthe government environment. This course begins tomap the changes in your existing processes to Agile.Course Outline1. Self-organized teams, even in a highly matrixedagency or organization.2. Simulate a project introduction, create a visionand set of light requirements.3. How to plan your product’s release within themandated 6 month timeframe.4. How to communicate project status utilizing bothAgile and EVM indicators for progress.5. How to satisfy the Office of Management andBudget (OMB) requirements (Circular A-11) whileapplying an Agile execution approach.6. Understanding customers and how to collaboratewith them to create User Stories.7. Relative estimating – focus on becoming moreaccurate rather than precise.8. Defining the distinction between capabilities andrequirements and when to document each.9. Identify Agile best practices as they relate tochallenges within the federal environment.December 8-10, 2014(Live virtual, noon – 5:30 pm)November 24-25, 2014Herndon, Virginia$1395 (8:30am - 4:30pm)"Register 3 or More & Receive $100 00 eachOff The Course Tuition."SummaryProject failures are often due to poor requirements gathering,analysis and planning. Traditional requirements documents may notcontain complete and accurate requirements due to rapidly changingbusiness environments. Agile requirements gathering, by movingdetailed requirements closer to implementation, allows for rapidresponse to change. "Collaborating and Communicating AgileRequirements" will show you how to gather and manage theserequirements. This two-day course will give you hands-on experiencewith techniques for gathering Agile requirements. Explanatory lectureswith demonstrations, combined with practice exercises will provide youwith the experience needed to create requirements that meet businessneeds.Course Outline1. Agile Overview. More than simply a methodology or approachto software development, Agile embraces a set of principles that drivemore effective software development. Agile focuses on the customer,embraces the ever changing nature of business environments andencourages human interaction in delivering outstanding software.2. Project Initiation. Among the key contributing factors leading toproject failure is poor communication between the customer anddeveloper groups. It is critical, therefore, that each successful projectstart out right.3. Focus on the Customer. It is critical that the customer be thefocus of a product throughout the development lifecycle. Everyrequirement should bring some value to the customer. Therefore, priorto defining requirements, it is important to define the customer.4. User Stories. User stories are a way to capture requirementsfrom a customer point of view. Stories do not capture all of the detailedrequirements, but require enough information to estimate and plan.5. Product Backlog. The Product Backlog is the complete list ofdesired elements, or requirements, for the product. It is NOT aRequirements Specification, but a high level identification of what thesoftware may satisfy. In this section we will discuss effective means ofcreating, prioritizing and maintaining the Product Backlog.6. Estimating and Planning. Among the greatest challenges indeveloping software and delivering against stakeholder expectations isestimating accurately and subsequently planning how thoseexpectations can be met. Agile cannot make that challenge disappear,but offers some very helpful tools that enable teams to set and meetthe appropriate expectations.7. Release Plan. The release plan identifies a goal for the storiesthat will be included for a release of the software. Through the priorprocesses, the team will have prioritized the stories and estimated theteam velocity. These key elements will come together to give the teama level of confidence that they can deliver the necessary requirementsfor a product release in what is normally a fixed timeframe.8. Use Cases. At the appropriate time, prior to entering into thedevelopment of a story, requirements will need to be discussed in moredetail. A proven method for documenting the appropriate detail from auser interaction point of view.9. Iteration Plan and Execution. An iteration is a fixed amount oftime in which stories/requirements will be developed, tested and readyfor release. Because the requirements communication process takesyou into each iteration throughout the product release, we'll explore theiteration planning and execution process.10. Retrospective on Communicating Requirements. UsingAgile Methods – Retrospectives are a key practice in Agile. We willtake an opportunity to review our learning collectively and how we canimprove. Each participant will identify one or two things that they willadapt in their working environment based on their learning. Theinstructor will also identify any elements of the course that should beadapted for a better learning experience, thus benefiting future courseparticipants.6 – Vol. 119 Register online at www.ATIcourses.com or call ATI at 888.501.2100 or 410.956.8805