Creating text-centric requirements documents is a time consuming activity, and trying to read and interpret them is cumbersome (and at times impossible) for your stakeholders. In this 1 hour session, you will learn how you can better define requirements, manage scope and collaborate with your stakeholders through the power of prototype-driven requirements that the unique features in iRise allows. The topics covered include:
- The benefits of prototyping in both a traditional and agile environment
- Understand the different levels of prototyping and when each should be applied
- Understand how prototyping can benefit the entire team
- How iRise integrates with other ALM tools
**There were many questions submitted at the end of the webinar. Below this video we've tried to answer some of them. If you have any other questions, please feel free to contact us at email@example.com
"How are Requirements in iRise integrated with JIRA?"
Requirement and user stories in iRise are synced in real-time with JIRA once the connector is setup. That includes all the attributes. Another nice benefit of the integration is that all the comments and conversations are synced too, so discussion between all teams (definition, dev, QA, etc...) can now happen. This helps kill the dreaded "silo" problem and fosters collaboration.
This page has a short video that actually shows an integration with JIRA in action: https://www.irise.com/features/integration/
"Do you intend to integrate with Microsoft TFS?"
"Any plans to integrate with MS TFS?"
"Can you integrate manager with MS Team Foundation backlog stories & iteration processes?
I'm not surprised that we received a lot of questions about TFS. It's one of our most popular integrations. We do integrate with TFS, and the process and benefits are the same as with our other integrations.
Trust me - if you're using MS TFS you'll want to talk with our integration expert. Click here to request a conversation. Watch this video to learn more.
"Can iRise interface with HP Quality Center?"
Yes. You can see a bit of a live integration near the end of this video: : https://www.irise.com/features/integration/
"Can you prototype during your req. elicitation session?"
Absolutely. Using iRise, the prototype will drive the elicitation and validation process. That's a big part of the magic. The prototype paired with inline requirements makes it much easier for you and your stakeholders to give feedback and validate the proposed solution.
This 3 minute vid gives a nice demo of the RM features and the elicitation process: https://www.irise.com/blog/2016/5/7/irise-tasktop-better-user-stories-innovative-results
"How is iRise prototyping used effectively in existing applications? Enhancements and improvements?"
For existing applications you have a number of options. You can drag screenshots into iRise and it will automatically create pages for you (shown in this fast prototyping video). You can then build functionality on top of it. You can also build custom widgets, libraries and masters in iRise that mimic your existing functionality and branding. These can then be used by anyone on the team to quickly build out enhancements.
"Do you suggest the business requirements are given to a BA or does the BA write down the business requirements?"
Every process is different, but the requirements tools in iRise can be easily customized to fit your process. Often the BA would use iRise to document the requirements, using the prototype to help drive the process. Some teams might be using JIRA or another ALM tool already when they adopt iRise, so they integrate and bring the "power of prototyping" to their existing tool set. I've seen situations where the team already has early documentation, user personas, high-level requirements at the start of a project - these can be added to iRise Manager. You can see examples of that HERE.
"How does iRise differ from (insert competitor here)?"
The three top features that come to mind when discussing what makes iRise special are real-time collaboration, requirement management + prototyping, and our integrations.
Real-time collaboration allows teams to work on the same projects and pages at the same time, seeing changes as they happen. This is especially valuable for large teams.
Requirements management + prototyping is the unique iRise feature set and process that allows teams to create accurate requirements.
Our integrations bring tracebiilty to the process, insures that EVERYONE is looking at the same information, and gives development and QA teams the ability to experience the functionality they're being asked to build or write test-scripts for (as opposed to just using text alone, which we know rarely works).
I could also talk about security, enterprises-grade options like on-prem install, etc...
"In my company I was brought in as a BA to use iRise, but UI/UX designers want to use sketch. How would you define iRise better than sketch?"
This is a common question that comes up when dealing with UX teams. Thankfully, designers are getting more comfortable with incorporating prototyping into their process.
iRise vs Sketch is not an either/or proposition. iRise actually empowers Sketch and UX designers by adding interactivity to their work and allowing them to convey their designs much more effectively. iRise make UX design a focal point of the process, allowing designers to import their assets into iRise and quickly create interactive simulations, including data driven functionality. They can then work with the team and iterate until they get the design and functionality right. The mobile capabilities are also very cool. :-)
The requirements management functionality in iRise allows the UX to get further integrated into the larger team and process - something they'll appreciate. And the prototyping serves as a interactive blueprint for IT, so ultimately what the UX team designs is what gets built.
"Can you create customized elements that we can reuse?"
In iRise you can create customized libraries, which can include both static and interactive widgets. These are available to the entire team in real-time. They're a great way to not only make prototyping easier and faster, but it can be used to ensure everyone's designs are consistent (with company branding or just because it will mean better design).
"We are using iRise for SAP CRM and I want to say it is Awesome. Our test, Change and End user teams are very happy especially with the level of interaction it provides."
Great to hear. :-) SAP applications, because they're often large, mission-critical projects, are a perfect spot for iRise. We have a long relationship with SAP and have seen amazing results.
"What are the challenges you have faced in managing prototypes and requirements while sharing with customers?"
Every project and customer is different, but I'd say that getting buy-in to the process up front (as mentioned as a best practice during the webinar) is an important way to help avoid challenges down the road.
Once members of the team start using iRise a a central communication hub, they'll be off to the races. No one likes to write or review traditional requirements documents - not business analysts, project managers, management, stakeholders, or developers. But sometimes prototype-driven requirements is a new process to them, so you need get the process started.
"Can you share examples of how you did (xyz) feature?"
"I saw a demo of a carousel in the webinar demo. Can you show me an example of how you did it?"
Our video tutorials have some great real-world examples: https://www.irise.com/support/irise-tutorials/
This video shows the creation of a carousel: https://www.irise.com/support/tutorials/basics/tutorial-introduction-to-views
You can also contact support through our website chat - they have a set of common samples they can provide.
"Can iRise prototype native/mobile applications?"
Big time. The features include mobile emulators on your desktop, a mobile app for on-device testing, free mobile libraries in the product, mobile actions like transitions, swipe, rotation, etc...
Learn more here: https://www.irise.com/mobile-prototyping/