Requirements Collaboration. March 22, 2012

Transcription

1 Requirements Collaboration March 22, 2012

2 Changing Change. Develop the Professional. Develop the Profession. International Institute of Business Analysis 2

3 Vision and Mission The world's leading association for Business Analysis professionals Develop and maintain standards for the practice of business analysis and for the certification of its practitioners IIBA is an international not-for-profit professional association for business analysts. 3 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

4 Tom Karasmanis IIBA Product Manager Tom Karasmanis is a Senior Consultant with 25 years' experience in Information Technology, including roles as a Business Architect, Business/Systems Analyst, Project Leader, Technical Architect, and Software Engineer. He has worked in publishing, healthcare, public sector, banking, financial services, insurance, supply chain, telecommunications, and retail. Tom served as Chief Architect of the IIBA from 2009 to He is currently IIBA Product Manager of Being a BA: Technical Excellence and Vendor Showcase. Tom is a management consultant in business architecture and business analysis, assisting organizations to build or improve their BA practices. He speaks regularly at international conferences. Tom holds a Bachelor of Applied Science in Chemical Engineering from the University of Toronto and is active in the business analysis and business architecture communities. ( C ) I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 4

5 Outline Introductions and Housekeeping 12:00 Vendor Presentations 12:05 Seapine Software 12:05 Yonix 12:20 Jama Software 12:35 Questions and Answers 12:50 Close 12:59 Extended Q&A 1:00 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 5

6 Purpose Teamwork (8.5.3) Business analysts must be able to work closely with other team members to effectively support their work so that solutions can be effectively implemented. 6 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

7 Definition Teamwork (8.5.3) Working as part of a team with other stakeholders How do teams form and function? 7 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

8 Definition Teamwork (8.5.3) Communications and trust can also be enhanced through understanding and awareness of facets such as the process of setting of rules for the team, team decisionmaking, formal and informal team leadership and management roles. I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 8

9 Definition Teamwork (8.5.3) Team conflict is quite common. If handled well, the resolution of conflict can actually benefit the team. 9 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

10 Definition Teamwork (8.5.3) The basic types of conflict are emotional and cognitive. Emotional conflict stems from personal interactions, while Cognitive conflicts are based upon disagreements on matters of substantive value or impact on the project or organization. I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 10

11 Definition Teamwork (8.5.3) Resolution of cognitive conflict requires the team to focus on examining the premises, assumptions, observations and expectations of the team members. I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 11

12 Measures Teamwork (8.5.3) Teamwork skills are demonstrated through: Fostering a collaborative working environment Effective resolution of conflict Developing trust among team members Support among the team for shared high standards of achievement Team members have a shared sense of ownership of the team goals I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 12

13 Question and Answer How to Ask Questions Use the Question box to ask questions. Selected questions will be answered at the end, but you can ask at any time. Include the vendor s name if you want a specific vendor to respond. Short, specific questions, please! IIBA Host Tom Karasmanis Peter Varhol Jody Bullen John Simpson 13 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

14 Requirements Collaboration Peter Varhol Seapine Software

15 About Seapine Software Process-centric product development solutions In business since ,500+ customers

16 Why should we care about collaboration? Reduce rework More effective reviews and approvals Focus the team Speed time to market Boost team efficiency Drive product quality

17 Focus on Implementation Teams BA is the bridge between market and project teams Collaboration improves understanding and agreement on the product Goal is higher product quality (fit and function)

18 Keys to Project Success Early involvement by project team Early and detailed requirements reviews Insight into impact of requirements

19 Early Involvement by Project Team Sharing requirements in early stages of analysis Awareness of changes and comments as they occur Participating in discussion threads Helping to clarify issues Q&A with all stakeholders Encourage early ownership of requirements by the team

20 Requirements Review and Feedback Call out specific requirements for review Meetings are focused and provide actionable results Preliminary work is accomplished before meetings Feedback is tracked to ensure response and action

21 Understanding Impact of Requirements Requirements impact technical approach and schedule Collaboration can refine requirements while optimizing resources Understanding impacts helps promote agreement on how to best structure and deliver product features

22 Seapine TestTrack and Requirements Collaboration Familiar approach to requirements creation Manage all requirement artifacts Details threads Workflow Versions Documents Links and attachments History

23 Seapine TestTrack and Requirements Collaboration Facilitate effective reviews Improve quality and reduce time for reviews Save BA time in gathering feedback and approvals Workflow and sign-offs Process and understanding must be complete

24 Summary Requirements collaboration is key to a successful project Early reviews make implementation teams partners in the process Timely and transparent feedback contribute to understanding and agreement Workflows add structure and bring closure Seapine TestTrack brings collaborative features to the process of building great products

25 Thank you For more information Seapine Software: The Seapine View:

26 Capture, Communicate, Collaborate Jody Bullen CEO and Founder NZ BA of the Year

27 Analysis, not Administration Designed by BAs for BAs Passionate about Business Analysis Wellington, New Zealand Trusted by Councils/Government, Banks, Health Boards

28 The common story of Requirements Communication and Collaboration

29 Requirements Communication & Collaboration in 6 steps Create a Yonix Document Add Content Add Requirements Define Terms Publish a Version Invite and Collaborate

30 1 Create a Yonix Document Project Tab Search Everything Import from MS Word or Excel, create from a template or create your own. Document Sections Content and Requirements Filter Add Stakeholders Template common documents Concurrent access Automatic versioning and auditing Tailor documents for stakeholders Sub Sections Collaborate on all your documentation in one place

31 2 Add Content Create tables, embed images, and use rich text formatting to communicate your requirements. Section Text Embed Images Inline Editing Copy and paste images Inline Spellchecker Image Libraries Rich text Formatting Collaborate on content, files, models and images

32 3 Add Requirements From your libraries to document sections or create new ones in-line. Document Sections Requirement Groups Create New or Insert Existing Create requirements types to match your process and reuse these across your projects. Inline Creation and Editing Inline editing + versioning Single point updates Requirements traceability Drag and drop requirements Customizable requirement hierarchies Collaborate on all your requirements in one place

33 4 Define Terms Store and reuse terms and definitions to prevent misunderstandings, saving you hours of explanations and headaches. Embed Terms Inline Definitions Share dictionaries across projects Reuse common terms Automatic synchronization Reuse Terms Collaborate on terms

34 5 Publish a Version Baseline your Yonix Documents or publish a version to MS Word. Export Requirements to Excel Upload your files and images, or link to the file using a URL. Document Versioning Professional Word Output Microsoft Word output Customizable output templates Document versioning and baselines Collaborate on versions

35 6 Invite and Collaborate Invite team members and stakeholders to review, validate, discuss, share their thoughts, and provide feedback on your documents and requirements. Comment on everything Join and Track Discussions Assign Ownership and Roles Inline comments and discussions Automatic notifications Discussions views Collaborate on everything!

36 Requirements Collaboration in action

37 Yonix makes Requirements Collaboration easier Analysis, not Administration Build consensus faster Better requirements Improve business outcomes Retain and reuse knowledge The stand out features in Yonix are collaborative documents and the output to Word; very professional, very easy to do and very quick. Kate Fox - Senior Business Analyst "Yonix makes the whole process of managing and versioning requirements simpler and more transparent. Scottie Henderson - Senior Business Analyst

38 Capture, Communicate, Collaborate Claim your Complimentary 1 year subscription for you and five stakeholders Offer is limited to the first 100 BAs So claim yours now at

39 Requirements Collaboration IIBA Vendor Showcase Series March 22, 2011

40 John Simpson Vice President Based in Portland, Oregon Requirements management solution Fortune 500 & government agencies

41 Technology Financial services Media / telecom Healthcare / medical faster improved 2x 2x 25% development quality reduced costs Defense contractors Government Aerospace Education / non-profit

42 It s about the people. The secret to success is to keep everyone connected.

43 Does everyone understand what we re building and why?

44 Old Way: Death by Documents

45 Business PM Analyst Development & QA Business Stakeholders Meeting Document Review

46 Meeting Document Review Feedback Meeting 2 Version 2 Review 2

47 Version 2 Old Way: Using Track Changes in Word

48 New Way: Requirements Collaboration

49 Customers Exec Sponsors Collaborative requirements management solution: Collaboration: Review & approve scope Traceability: Relationships & impact analysis Test Coverage: Create & execute test plans Change Management: Detailed version control Project Leads PM s & BA s Developers & QA

50 Step 1 Invite your team to the review to gain clarity and shared vision of the project

51 Step 2 Gather feedback from everyone involved and in context to the specific requirements

52 Step 3 Monitor feedback to track progress and proposed changes to requirements that still need work

53 Step 4 Make edits to the changed requirement in context to the feedback to reach agreement

54 Step 5 Capture approvals and electronic signatures

55 Thank you. John Simpson Vice President, Jama Software Watch the video of the Review Center: Get requirements collaboration whitepapers:

56 Question and Answer How to Ask Questions Use the Question box to ask questions. Selected questions will be answered at the end, but you can ask at any time. Include the vendor s name if you want a specific vendor to respond. Short, specific questions, please! IIBA Host Tom Karasmanis Peter Varhol Jody Bullen John Simpson 57 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

57 Contact Information Register for more webinars on the Professional Development page of our website under Webinars. IIBA.org/PD community.iiba.org Peter Varhol Seapine Software Jody Bullen YONIX John Simpson Jama Software ] International Institute of Business Analysis 58