Getting started with Auroria
September 22, 2019 in Tutorials
Getting started with new software tools can be hard by itself. Of course we aim to make using Auroria as simple as possible, but sometimes a helpful hand, or blog entry in this case, can still be helpful. So lets get going...
Auroria is an agile project management solution tailored for ease-of-use for developers as well as non-tech people, e.g. project managers, scrum masters, ... .
It's goal is to provide a software that "scales with your project" - the SCRUM way. No matter if you have a large organization you'd like to move to Auroria, or a small startup with a just started software project.
By providing you with a lot of different features or "add ons" if you want so, to enhance your management workflows, it's perfectly suited for nearly every workflow of any project.
Well, as a first step a registration would be very manadatory. Don't worry, the registration and the basic features of Auroria are and will always be free of any charge. If there are any charges upcoming, we are anyways going to warn you about them and ask for your payment details before allowing you to enter the "danger/payment zone".
After you have signed up, your very own "Organization" is being created for you automatically.
Think of your organization like your "top-level" domain. This is where you are able to manage everything important within your domain of work.
- You are able to create and manage your different projects.
- You are able to define roles for different users, and assign those roles different permissions.
- You are able to manage your enabled features, view your invoices.
- And lot more, we are not covering in this guide.
So for small to middle sized enterprises an organization could bascally be a mirror of all the people and working in it. For large enterprises or highly sophisticated teams, an organization could also be your department of some kind. Have it either way, or totally different, we are happy as long as you are happpy with your choice.
You are able to create as many organizations as you want, and it's also possible for one user to be in multiple ones. Think of slack workspaces if you want to.
So after you've set your organization up the way you want it to be (or not, we try to serve with well defined defaults for basically everything), it would be time to create your first project!
Creating your first project is easy. The very site you are directed to after you've signed up, is the project overview page. Since you haven't created any projects yet, the only thing possible here is to create a project. So hit the "Create" button and fill in the name, and optionally a description of your project. These values can always be changed later on.
After creating your project, you are welcomed with a for now little bit empty dasboard and a new sidebar to the right waiting for your navigation commands.
Navigate right to the menu entry "Backlog".
This is where all the preparations happen. In your backlog you are able to create, delete and manage all the work that is going to be done within the lifecycle of your project. You can create different userstories or bugs. Assign those to Versions, Epics and create subtasks for your work.
Whenever you are done or at least done for now creating work packages, it would be time to create a new sprint for your development team by clicking the side-bar entry "Sprints".
Within this view you are able to see all the upcoming, the current, and the past sprints of your team.
Here you are also able to create new sprints, so go ahead and create one with a name you and your time like.
After assigning all the work packages to the sprint, by simple drag and droppping them in the backlog section, you are ready to start your sprint.
After you've successfully started your sprint, the board will fill with all those work packages you have just created. Within the sprint section, you also have the ability to assign those packages directly to your project members, so everybody knows how much work he is able to do, and how much work needs to be done.
By dragging those packages, called "subtasks", accross the board into the last column, you are tracking the progress of the work your team is doing.
After the sprint is over, or all the packages are in the last status column. You can stop the current sprint, and start a new one, repeating the steps from above until you and your team conquer the world with your new software project.
This is it, these are the very basic steps it takes to get going and using Auroria for your software development workflows.