CEG offers Corporate Training and Consulting, as well as traditional and virtual instructor-led courses in management and leadership, project management, business analysis, business process management, agile/scrum, and lean six sigma.
Issue link: https://info.corpedgroup.com/i/1514449
A Q U I C K P R I M E R O N AG I L I T Y A N D S C R U M User stories are found during initial story writing workshops as well as during development and during end-of-iteration reviews. In fact, new stories can be added to the "backlog" at any time. Story Card Layout User stories are commonly written on index cards. The story state- ment is on the front along with relevant details and the story's "size." The back of the card lists the minimum done criteria whose implementation would be consid- ered a successful implementation of the story by the product owner. (See Figure 4.) User stories intentionally do not capture a lot of details because a story may never get implemented if it is not of high enough priority, and the story details may change by the time implementation starts. Since we don't capture much up front, this assumes that business users are engaged during imple- mentation since details are uncov- ered in conversations. Story Sizing Guidelines Smaller stories with a clearly de- fined goal are better. Large sto- ries that are high level and vague are called epics. Epics should be decomposed into several smaller stories. Ideally, a story should be implementable in a single iteration. Stories should be written at a high level; details should be omitted until implementation starts. Anyone can contribute a story: • Product owner • Users, analysts, and SMEs • Developers and testers Epics: Large Stories Large user stories are called epics. They contain more than one idea or feature and commonly come from managers. Users tend to give "click-level" requirements and features. Epics need to be split into smaller and more tractable user stories so that they lend them- selves to being implemented in a single iteration. Themes: Related Stories A theme is a collection of user sto- ries related by a common subject area. Iterations often address sto- ries from one theme as they tend to exhibit more interdependencies and also rely on the same infra- structure code. Story Writing Workshops Story writing workshops are a common approach for finding the initial user stories. Additional stories will be discovered by the developers and business analysts during iteration implementation as well as by stakeholders and the product owners during itera- tion reviews. New stories can be contributed by anyone at any time. New stories are simply added to the backlog of stories and will be addressed in a subsequent sprint if the story's priority is considered high enough. Stories are captured but not discussed in detail yet. Participants in a story writing workshop include anyone com- mitted to the project and must minimally include the product owner, users, developers, business analyst, and testers. Story Size Done/Success Criteria As a loan administrator, I want to be able to record a loan payment received from a student, so that the loan balance reflects the payment. • Interest and principal allocation • Student lookup F R O N T • Payment allocated correctly to principal and interest for loan • Loan principal reduced • Annual loan interest increased B AC K 30 Figure 4. User Story Cards