1 / 20

Winbook

Winbook. Process Implications of using Social Networking based Tools for Requirements Engineering. Nupul Kukreja Annual Research Review 6 th March 2012. Winbook. Agenda. Social Networking & Email. Theory- W. User Stories. Requirement Specifications.

jacob
Download Presentation

Winbook

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Winbook Process Implications of using Social Networking based Tools for Requirements Engineering NupulKukreja Annual Research Review 6th March 2012 ARR '12: USC-CSSE (c)

  2. Winbook Agenda Social Networking & Email Theory- W User Stories Requirement Specifications ARR '12: USC-CSSE (c)

  3. Software Requirement Specifications (SRS) Too much detail and too much to capture The true 3D view SRS - in 2D Delegate – Let’s create more communication overhead  ARR '12: USC-CSSE (c)

  4. Change Management & SRS? ARR '12: USC-CSSE (c)

  5. Along came a Story User Stories SRS What we thought… What was actually intended… ARR '12: USC-CSSE (c)

  6. The User Story – 3Cs A promissory note of intent Discussion & clarification of intent (a.k.a requirement) Acceptance Tests Card Conversation Confirmation Lightweight Ecstasy ARR '12: USC-CSSE (c)

  7. Theory-W STOP THIS MADNESS! Customer Dr. Boehm You can think of requirements as stakeholder negotiated win conditions!! Developer As a team discuss what will make each of you “win” (a.k.a. win conditions) Reach a mutual consensus and move forward (WinWin Equilibrium) Identify any issues and come up with options to resolve them ARR '12: USC-CSSE (c)

  8. Let’s see what the other humans were up to… ARR '12: USC-CSSE (c)

  9. Social Networking and Email facebook Gmail ‘click’ to ‘like’ (agreement) Organizing emails using color-coded labels Commenting – having a casual asynchronous conversation Poke (no real value) ARR '12: USC-CSSE (c)

  10. Putting It All Together Winbook Theory - W Requirement Specifications User Stories Gmail Facebook ARR '12: USC-CSSE (c)

  11. Winbook • A collaborative, social networking based tool for requirements brainstorming… • …with requirements organization using color-coded labels similar to Gmail… • …to collaboratively decide and agree on software system requirements reaching win-win equilibrium (based on Theory-W)… • …by keeping it short and simple like user stories! • Most recent incarnation of the WinWin negotiation framework – substantially improves on WikiWinWin ARR '12: USC-CSSE (c)

  12. Pre-Winbook Era • User expectations (win conditions)were recorded using WikiWinWin – cumbersome to navigate and update • Clients would rarely use it after first WinWin session • Teams would create a System and Software Requirements Document (SSRD) based on the win conditions – maintaining traceability to win conditions • Change management and synchronization overhead made teams only focus on the SSRD (falling back on email communication) • Requirements in the SSRD were back-referenced in the System and Software Architecture Document (SSAD) – another synchronization overhead • Too much effort overhead with traceability to win conditions and keeping the project ‘value focused’ • Extreme dissatisfaction expressed by student teams regarding WikiWinWin • Teams failed to understand the value of WinWin negotiations – it was just something to do as per the syllabus • Expectation inconsistencies within the team due to silo-ed/point-to-point email communication ARR '12: USC-CSSE (c)

  13. The Winbook Era • Experimentation of using social networking based paradigm for requirements engineering • Teams can ‘post’ win-conditions to a shared Wall that is accessible to everyone • For each win condition team members can raise issues, concerns or risks similar to ‘commenting’ on Facebook • Similarly, teams could suggest options for resolving the issues • Seamless signaling of ‘agreements’ – akin to clicking ‘Like’ on Facebook • A one-stop halt for gathering requirements on a shared wall accessible and updateable by the whole team ARR '12: USC-CSSE (c)

  14. Process Implications of Using Winbook • Partially auto-generated SSRD with traceability to win conditions eliminating overhead • Up-to-date rationale capture of stakeholders’ needs and sustained client renegotiation within the tool itself! • Improved effectiveness of milestone reviews – clients more involved in definition and prioritization of win conditions • Teams had better understanding of expectations and value propositions • Better understanding of the ‘value focused’ mindset – leading to value based channelizing of project activities • Color-coded equilibrium status kept everyone on the same page, faster ARR '12: USC-CSSE (c)

  15. Process Implications (Cont’d) • Eliminating the SSRD!! Various attributes (e.g. pre/post-conditions, priority) either captured in Winbook or SSAD – making SSRD redundant! • Win conditions capture-able as user stories  Wall = Product backlog with added dimensions of issues and options! • Institutional memory of the negotiation (i.e. WinWin equilibrium) captured and maintained throughout the course of the project – with very little overhead ARR '12: USC-CSSE (c)

  16. Winbook – Evaluation & Feedback • Clients expressed gratitude for such an easy to use framework that allowed for continual monitoring of the ‘commitment status’ of the team(s) • Increased ‘agility’ and participation of stakeholders (clients) – especially in a distributed setting • WinWin negotiations were ‘fun’ – students were hungry for more (sessions)! • LADOT expressed interest in deploying Winbook internally for collaborative brainstorming • Also adopted as part of project by major US Government organization for bridging gap between requirements and architecture ARR '12: USC-CSSE (c)

  17. Current Roadmap • End-to-end tool for Value Based Requirements Elicitation and Management • Capturing goals and benefits and linking ‘Win Conditions’ to them – facilitating goal oriented requirements engineering • Capturing ‘Acceptance Tests’ for Win Conditions • Visualization of ‘Work in Progress’ – similar to Kanban boards • Built-in support for playing Planning Poker for estimating Business Value and Ease of Realization ARR '12: USC-CSSE (c)

  18. ARR '12: USC-CSSE (c)

  19. ARR '12: USC-CSSE (c)

  20. Thank You&See you at the Winbook Workshop at 4 pm Q & A ARR '12: USC-CSSE (c)

More Related