Explore Yellowfin now with our sample datasetGet Started
What Skills are required to use Yellowfin?
To maximise the value of your data through Yellowfin a range of skills are required. These include: being able to prepare and manage data, data analysis skills to create analytic content like reports and dashboards, business analysis skills to be able to interpret and add context to data and development skills if you wish to extend the capabilities of Yellowfin through code.
Some people have all these skills, but mostly we recognise the need to build a team of people across the business to be most effective. These teams can exist for a short time – to deliver the project or be ongoing to continuously create and deliver new insights to the business.
A team may consist of one or more of the following:
How does Yellowfin support different user profiles?
Yellowfin is designed to support the spectrum of users who are necessary for building enterprise analytic solutions. This includes line-of-business experts and self-service users, business analysts, data analysts, data engineers and professional developers. Each of these roles can collaborate in Yellowfin through an integrated set of tools across the entire analytics development lifecycle – from data preparation to dashboard creation and management reporting through stories.
How does Yellowfin support team-based development?
Project team members are connected instantly and interactively to changes and updates to new content such as meta-data layers, dashboards and stories via approval and collaborative creation processes – in addition to being notified of changes via their timeline. All of which provide the opportunity for feedback loops from end-users. This framework is the backbone for the Yellowfin collaborative process, while visual blueprints and drag-and-drop WYSIWYG editors lower the barrier to entry for business users to participate in the development process.
Can more than one person work on developing new content?
There are two ways that Yellowfin supports multi-user authoring.
One method is to pass content from one user to another. In this case the content is published and subsequent authors create and edit new versions of the content – where each user works on one working version of the content at any one time. Essentially handing development from one user to another.
The other method is where one or more additional users are invited to collaborate on a piece of content development prior to that content being published. In this scenario users that are invited are able to work on the non-published content collaborating more closely to create a final version of the content.