Sheet 1
Risk Analysis Heuristics XMind
Product: X-Mind
Charter: UX/UI Product Risks
  Project Factors
Approach: Internal Team Member w/No Existing Development
    Learning Curve
      Prior Experience & Knowledge
        What existing experience, knowledge, perspective, biases...
          Do Developers have?
            Ever coded for a mind-mapping software before?
          Do Testers have?
            Ever written test strategies for a mind-mapping software before?
          Does the PO have?
            Ever engaged with customers on this or a similar product offering?
          Does the SM have?
            Ever solved team struggles related to mind-mapping software or related features?
        Did anyone on the team previously work for a company that made a competing product?
      Any external-industry UX/UI practices being applied out of context? (intentional avoidance to reevaluate presuppositions)
      Existing UI/UX Assumptions
        What assumptions are being made about how mind-mapping should work?
        Any conflicts between assumptions?
        Any assumptions about how mind-mapping UI should be laid out?
        Any unspoken assumptions?
    Poor Control
      Who'd doing the UX/UI code reviews?
      Does DoD (Definition of Done) include team reviews?
      Are UX/UI architects involved in creating mock-ups
    Rushed Work
      Wireframes/Mockups created in a vacuum vs. with the support of the whole team?
      Accuracy of UX/UI Estimates
      Constant communication on customer UX/UI expectations?
        To UI Developers
        To Frontend Testers
    Fatigue
      Is Product Management tuned in to cultural factors that can determine quality of UX/UI work? Such as:
        Team Capacity
        Team Velocity
        Individual Abilities
        Cultural Dynamics
        Health Issues
    Overfamiliarity
      External UX/UI Reviews
        External Developers
        External Testers
        External Product Managers/Owners
        Can dividing UX/UI components across multiple teams help mitigate this?
        Can User Testing (UAT Environment) help mitigate this?
        Can bringing in contractors that rotate on/off the project teams help mitigate this? (provide fresh/new eyes)
    Third-party Contributions
      Limit dependencies: Try to use as little 3rd party UX/UI content as possible (e.g. roll your own framework from as simplified a boiler-plater as possible)
      Time-management (No unwarranted testing): Test only XMind UX/UI integrations, not the 3rd party's
    Distributed Team
      Agreement early on in the project on...
        Release scheduling
        Scrum ceremony scheduling
        Best method of communication (email, chat, phone, video, etc.)
        Work Hours (static, flex, alternating, cadence, etc.)
      Ensure all meetings be are as 'human-like' as possible
        E.G. 1) Phone Conference, Not Text Chat
        E.G. 2) Video Chat, Not Phone Conference
    Bad Tools
      SM should be in tune with tool/tech frustrations and quickly escalate
        Dev relationship with SM
        Tester relationship with SM
        SM ability to facilitate Dev/Tester communication
    Expense of Fixes
      Model Usage (Team adoption)
        Use of test strategies that address UX/UI concerns
        HTSM > Charisma & Usability
        Use end-to-end (From backlog grooming to Release)
      Product Management Prioritization
        Based on user feedback, expectations - should prioritize UX/UI bug importance
          E.G. Can we push out with KNOWN bugs w/o affecting company image or profitability?
        Otherwise, unnecessary time sink for the team
        Team Needs business direction (bus. priorities) on which defects are 'worth' their time
        Backlog Decision
          Which makes more sense?
            To have one? (with priorities/severities)
            Not to have one (DoD includes fixing ALL bugs as they are found)
    Not Yet Tested
      Determine how much time (sprints) team can dedicate to untested areas (implies No new feature development)
      Developer brain dumps
        With Product Owners
        With Testers
        Known UX/UI concerns (from coding perspective)
  Technology Factors
Approach: External User w/Completed Application
    New Technology: Over time, the risks associated with any new kind of technology will become apparent, so if your product uses the latest whizzy concept, it is more likely to have important and unknown bugs in it.
    New Code:
      New Feature
        Visit the XMind website and see if we can obtain a feature update list that could be used to hint toward code changes
    Old Code:
      Old Features
        Visit the XMind website and see if we can obtain a feature update list that could be used to hint toward code changes
    Changed Code: Any recently changed code is more likely to have unknown problems.
      Updated Features
        Visit the XMind website and see if we can obtain a feature update list that could be used to hint toward code changes
    Brittle Code: Some code may be written in a way that makes it difficult to change without introducing new problems. Even if this code never changes, it may be brittle in the sense that it tends to break when anything around it changes.
    Complexity:
      Locked Features of Application
        Encrypt with Password (Pro)
        Audio Notes (Pro)
        Presentation Mode (Pro)
        Brainstorming Mode (Pro)
        Gantt Chart (Pro)
        Task Info (Pro)
        Search (Pro)
        Search On Web (Pro)
        Clip Art (Pro)
        Index (Pro)
        Advanced Filter (Pro)
        Map Shot (Pro)
        Merge (Pro)
        Extract Style (Pro)
        Extract Theme (Pro)
        Export Xmind Resource Bundle (Pro)
        Export Types
    Failure History: The more that a product or part of a product has failed in the past, the more you might expect it to fail in the future. Also, if a particular product has failed in a particularly embarrassing way, it perhaps should not be allowed to fail in that way again without bring the project team into disrepute.
    Dependencies Upstream: One part of a system or one feature of a product may depend on data or conditions that are controlled by other components that come before it. The more upstream processing that must occur correctly, the more likely that any bugs in those processes may cause failure in the downstream component.
    Dependencies Downstream: Any particular component that has many other components that rely on it will involve more risk, because the upstream bugs will propagate trouble downstream.
    Distributed Components: A product may be comprised of things that spread out over a large area, connected by tenuous network links that introduce uncertainty, noise, or lag time into the system.
    Open-Ended Input:
    Hard to Test:
      Hardened Application
      Locked Features
        Scenario Testing should be a consideration
    Hardware:
    Summary
      Use recent Changelogs to gather information
Time Trial Testing - Episode 2
by Connor Roberts, http://pixelgrill.com
& Brian Kurtz, https://twitter.com/kurtz74
Charter: UX and UI Risks for the X-Mind Product using James Bach's and Michael Bolton's Risk Analysis Heuristics (for Digital Products): http://www.xmind.net/m/bJvQ/
Things going on in projects, among people, may lead to bugs.
When developers are new to a tool, technology, or solution domain, they are likely to make mistakes. Many of those mistakes they will be unable to detect.
Code and other artifacts may not be under sufficient scrutiny or change control, allowing mistakes to be made and to persist. Also people may try to subvert weak controls when they perceive themselves to be under time pressure.
The amount of work exceeds the time available to do it comfortably. Corners are likely to be cut; details are likely to be forgotten.
Programmers and other members of the development team are more likely to make mistakes when they're physically tired or even just bored.
When people are immersed in a project or a community for an extended time, they may become blind to patterns of risks or problems that are easy for an outsider to see.
Any part of a product contributed by a third-party vendor may contain hidden features and bugs, and the developers may otherwise not fully understand it.
When people are working remotely from each other, communication may become strained and difficult, simple collaborations become expensive, the conditions for the exchange of tacit knowledge are inhibited.
The project team may be saddled with tools that interfere with or constrain their work; or that may introduce bugs directly into their work.
Some components or type of bugs may be especially expensive to fix, or take a long time to fix (platform bugs are typically like this). In that case, you may need to focus on finding those bugs especially soon.
Any part of the product that hasn't yet been tested is obviously likely to have fresh bugs in it, compared to things that have been tested. Therefore, for instance, it may be better to focus on parts of the product that have not been unit tested.
The structure and dynamics of technology itself may give rise to bugs.
The newer the code you are testing, the more likely it is to have unknown problems.
A product that has been around for a while may contain code that is unsuited to its current context, difficult to understand, or hard to modify.
The more different interacting elements a product has, the more ways it can fail; the more states or state transitions it has, the more states can be wrong.
The basic features of this application are free to use, but can I find a way to subvert security in the UI. <-- $$$ loss if so
The greater freedom there is in data, the more likely that a particular configuration of data could trigger a bug. Lack of filtering and bounding are especially a problem for security.
When something is hard to test, perhaps because it is hard to observe or hard to control, there will be greater risk that bugs will go undetected, and it will require extra effort to find the important bugs.
Since this is already a hardened application and the mission is UX and UI I don't feel that we are at high risk that this would be hard to test.
Locked features have no visual indication that you must upgrade until mouse over or on click.
Hardware components can’t be changed easily. Hardware related problems must be found early because of the long lead time for fixing.
All Changes of XMind 6 (v3.5.3)
Fixed Bugs
Fixed an issue that causes the Linux 64-bit install package not to work.
Fixed an issue that causes some Korean and Chinese fonts can not show normally on the map.
Fixed an bug that the width of topic can not be changed in Brainstorming mode.
All Changes of XMind 6 (v3.5.2)
Improvements
Add a language change option to Preferences.
Improve theme usage experience. When applying a theme, users can now choose from overriding all custom styles in the target map or keeping them.
Improve export experiences.
Add Danish and Japanese "Welcome to XMind" map guide under help menu.
Modify the translation errors in Japanese, Russian, French language pack.
Fixed Bugs
Fixed an issue that causes some text to disappear after exporting to PDF (Map) on Ubuntu.
Fixed some issues that cause XMind to crash after exporting to Microsoft Word and PDF Document on Ubuntu.
Fixed an internal error occurred during: "Template Image Loader".
Fixed an error while saving to Evernote under the Drill Down mode.
Fixed a bug that causes the exported Microsoft Project file to contain Chinese text.
Fixed an issue that causes "export to Microsoft PPT" not working.
Fixed an issue that causes XMind to crash while using "Alt +DownArrow" shortcut under Filter mode.
Fixed a bug that causes text typed in editing box to disappear after switching between sheets.
Fixed an issue that the wallpaper can't be removed after set by a theme containing it.
Fixed a bug that causes file hyperlinks pointing to LAN locations to be recognized as relative paths.
Other minor bug fixes.
All Changes of XMind 6 (v3.5.1)
Improvements
Adds Italian language pack.
Updates language packs of German, French, Danish, Japanese, Korean, Simplified Chinese, Traditional Chinese, Brazilian Portuguese.
Changes the default format of image export to PNG.
Fixed Bugs
Fixes an issue that makes style function not able to be used on Ubuntu.
Fixes an issue that causes the idea factory not available in brainstorming mode while using multiple displays.
Fixes a bug that makes the sheet style lost after extracting or saving a new theme.
Fixes an issue that sometimes causes failure to export to Microsoft Powerpoint.
Fixes an issue that cause some hyperlinks to fail to be redirected correctly.
Fixes some error that happens while import/export MS Word/PPT/Project.
All Changes of XMind 6 (v3.5.0)
New Features
All New Designed "Brainstorming Mode".
Save to Evernote.
Advanced Theme Editor.
Index View.
Export to Microsoft Project.
Export to Open Office (ODF).
More themes, styles and markers.
Import & Export XRB/XMind Resource Bundle.
Improvements
Add permissions in Local Network Sharing.
Reorganized and improved toolbar, customize toolbar position.
On Mac, XMind embeds Java 7 and no need to manually install Java anymore.
Integrate Style View into Properties View. Add "reset style" option.
Reorganize View Menu, add a sub-menu instead of the Views Dialog.
New style notification window.
New Sheet From Template.
An option to hide paid features from menu and toolbar.
Add a new balanced map structure.
Improved context menu.
New color picker.
Improved Export to Excel.
Add 120% value between 100% and 150% when zoom in/out a map.
Many other minor improvements.
Fixed Bugs
On Windows (Portable version) and Ubuntu, the splash image won't disappear after XMind was successfully launched.
When copy a link onto a topic in XMind, after export to PDF document, the link was failed to be opened.
Part of task text was cut off in Gantt View.
Fail to change the duration by dragging the task bar in Gantt View.
The background color of a image/marker in a topic was covered in black or changed after exporting to PDF Map.
The keyboard shortcut Ctrl + "+/-" can not be used to zoom in/out in Presentation Mode.
In Task Info View, if the text content of a task is too long, all buttons on the right side will not be displayed until the text content is displayed in full.
The internal web browser can not be used on Ubuntu.
Fail to open attachment(s) after exporting to PDF Document.
After exporting to Word, absolute link and relative link to file and folder are both failure; after exporting to HTML, only the relative link to file is failure.
Fail to import MS Word files that contain Table(s).
When main topic select a numbering style, the subtopic of floating topic can not select the same numbering style.
The MindMapEditor is not dirty when editing notes in the floating notes editor, which causes that you will not be prompted to save the modified notes while directly closing XMind.
Entering brainstorming mode while a topic is in edit mode will lead to mishandling of keyboard event.
Relative hyperlink becomes absolute link in the exported PDF Document file.
"Numbering Level Until" setting will be invalid after exporting to Word if the file has already included numbering.
AutoNumbering was removed after exporting to Excel.
The text's background of notes will be black after exporting to Word if the notes include bold font.
The notes shows normally after importing a Mindmanager file into XMind. But after exporting from XMind to PDF Document and Word, the notes part will be filled in black.
Part of contents was lost in XMind after importing from Word.
On Windows, there may be a prompt to stall Bonjour service everytime while launching XMind.
Many other minor bugs fixed.