Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Visual software design with themes and epics


Published on

Idea Camp at Scrum Gathering Amsterdam

Published in: Technology, Business
  • Be the first to comment

Visual software design with themes and epics

  1. 1. Helsinki, Tampere, Turku, Stockholm, Göteborg | Business is evolving, you should too. Visual Software Design with Themes and Epics Idea camp Scrum Gathering, Amsterdam 16.11.2010 Pentti Virtanen, Tieturi Oy 9.11.2010Copyright © Tieturi 1
  2. 2. Me and agenda • Pentti Virtanen • Ph.D., CST • Tieturi • Training and coaching company in Finland • Informator in Sweden • Agenda • Introduction • 15 min • Let’s do it • 30 min • Retrospective • 15 min 9.11.2010 Copyright © Tieturi 2
  3. 3. Big Picture of Agile Software Design 9.11.2010 Copyright © Tieturi 3 Product vision Product backlog Stories Sprint backlog task Increment of functionality Testing Feedback
  4. 4. Product vision • Concise statement that • Clarifies the scope of the new product • Enough for funding • Helps to keep the development focused and consistent • Communicated effectively • Formats: A3,Executive summary, Wall, Vision document • States • Customers and users of the software • Needs addressed • Most important product attributes • Revenue model • May compare the product to other products Certified ScrumMaster - version 2.4 4 Metaphor: 1. How do we do better visual product visions
  5. 5. Theme, epic, feature and user story • Feature is a valuable functionality • Theme is a collection of related features • Epic is a large feature • User story is a description of desired functionality told from the perspective of the user or customer • User stories are used to describe features, epics and themes Theme Epic Feature(User story) Certified Scrum Product Owner - version 1.3 5 Calendar As a clerk I want to use calendar functionality As an clerk I want to create a new course event so that the meeting is saved into calendars of the trainer and the class 21.11.2010
  6. 6. Product backlog “My mobile device” 9.11.2010 Copyright © Tieturi 6 Theme Epic Feature Games Navigation Pac man Sudoku Maps Cameras Tracking profile 2. How do we do better visual product backlogs
  7. 7. Augmenting user stories • In Agile and Scrum big frond- end design is depreciated • Time-boxes limit the time to use in requirements and design • Forces to go ahead with just enough information • Use augmentation only when necessary • Keep as light as possible • User centric design emphasizes UI designs to help users understand the requirements • Storyboards • Mockups ( PostIt-notes) • Prototypes • Other examples: • Spreadsheet showing business rules • Diagram showing a work flow • Remember: product owner is available for the Team during the Sprints ! 21.11.2010 Certified Scrum Product Owner - version 1.3 7 3. How do we do better visualization of user stories
  8. 8. Agile development Certified Scrum Product Owner - version 1.3 8 • Goals • Sprint backlog • Dashboard • Product vision • Architecture vision • User stories • GUI sketches • SW design P TP T A W P C Wall Emerging software 21.11.2010
  9. 9. Acceptance tests • User stories are commonly refined with acceptance tests • Exceptions, alternative scenarios • In XP a tester helps the customer to create automated tests • Can be expressed in a table format IN • Values of the input variables • …. ACTION • Description of the invocation of the functionality ( e.g. button click) OUT • Values of the output variables • … Certified Scrum Product Owner - version 1.3 921.11.2010 4. How do we do better acceptance tests ? Visual ?
  10. 10. 10 Certified Scrum Product Owner - version 1.3 Agile testing • Goal not to detect errors but improve programming, design … • Test harness prevents errors 10 C T P C T P Spec Vision Code Test cases Equal ? Code that Implements tests Automated test that Define requirements OK? 21.11.2010 5. How do we do better collaboration?
  11. 11. Let’s do it How do we do 1. better visual product visions 2. better visual product backlogs 3. better visualization of user stories 4. better acceptance tests ? Visual ? 5. better collaboration 6. better ... 9.11.2010 Copyright © Tieturi 11
  12. 12. Case: FIFATix Product • FIFA has decided to develop dedicated website (known as FIFATix) for electronic ticket sale and resale. Background: • In some cities, such as Milan, almost all games are sold out and obtaining tickets through normal channels is nearly impossible. The resale of tickets at a profit is illegal and prohibited by the FIFA rules. Because available auctions like eBay are used to scalping regardless of the rules, FIFA sees that scalping can be prevented only by its system (FIFATix). Functional requirements • Register potential sellers of tickets and assign them a userid and password • Give staff members of football clubs and other game organizers including FIFA, UEFA etc. individual userids • Register potential buyers of tickets and assign them a userid and password • Maintain profiles under the userid, including organization, email, addresses, preferences, and credit card information • Sellers can make tickets available at a fixed price, which buyers can pay in full via credit card. • Transferring electronic tickets from sellers to buyers • Printing electronic tickets • Checking electronic tickets at stadiums • Placing tickets up for auction. Telling a floor price, start of auction time/date, end of auction time/date and verified ticket information (game days, teams, number of seats located next to each other and the seat locations). • Conducting an auction for the tickets to registered buyers. • Successfully concluding the auction by awarding the tickets to the highest bidder by the end date and, at the same time, debiting the buyers credit card and placing the funds in a FIFATix account. • Notifying the buyer and the seller of the successful sale of the tickets • Transferring the funds for the ticket sale less 25% to the seller • Transferring the 25% plus any interest to a corporate FIFA account from the FIFATix account automatically. • Disqualifying the resold tickets so that only buyers can have printed tickets that are valid in the stadiums • Providing information inventory and inventory search capabilities for teams, stadiums, games, tickets, dates, and seats. • Providing for advertising and promotions on FIFATix. • Ability to identify and ban abusers of FIFATix. Nonfunctional Requirements: • 99% availability 24x7. • Secure for the level of financial activity envisioned (2,000 tickets per day at an average price of $50). • 250,000 simultaneous users with sub second response time. • Scalable to 1,000,000 simultaneous users as needed. 9.11.2010 Copyright © Tieturi 12
  13. 13. Retrospective • What went well? • Ideas you want to promote • What should be improved? • Something that you tried and did not work 9.11.2010 Copyright © Tieturi 13