All Collections
Getting started
Day 1 with BigAgile: Setup checklist
Day 1 with BigAgile: Setup checklist

Welcome to BigAgile. We put together this quick guide to help you get started with setting up your product on day 1.

B
Written by BigAgile Support
Updated over a week ago

Step 1: Import your task management data (10min)

Once you've logged into BigAgile, make sure to import your existing task management data. BigAgile integrates with all major tools like Jira and Azure DevOps, making it quick and easy to plug in your tool of choice. To accommodate all your needs regardless of the size and complexity of your organisation, we have set no limits to the number of Jira and/or Azure DevOps instances you can import. Additionally, each instance connector can consist of as many teams as you need it to, ensuring all of your work is surfaced in a single, easy to use and visualise BigAgile instance.

Need help with importing your task management data? Check out our Jira Integration article.

Step 2: Add Users (1-2min)

Adding users allows you to collaborate with your peers and teams, as well as provide transparency to stakeholders. It is quick and easy and there is no limit or cost associated with the number of users you add. All you need is your colleague's email address.

Step 3: Setup your Increments (5min)

Why do I need to set up Increments?

Setting up your Increments is vital to the system-wide functionality in BigAgile. Increments will allow you to plot all your work on the development timeline giving you the visibility you need to:

  • Effectively manage the successful delivery of your current work by selecting the 'Active' Increment

  • Enable structured and effective reflection on past work via our Scope Change view - e.g. surfacing trends emerging in a previous ('Complete) Increment can inform your improvement opportunities or help you understand where improvements are already happening

  • Create and articulate your strategic plan via Roadmaps

  • And via Product Kanban

  • Make your delivery estimations as accurate as possible via Program predictability insight

Did this answer your question?