jason-goodman-vbxyFxlgpjM-unsplash

Agile Project Management using Ruly

Ruly's agile project management tool is a full-featured product that is ready to use to start managing software projects, out of the box. This application is included, as an installable app with the Ruly platform.

Using a tool to manage the software development process is essential to increasing both productivity and quality. Ruly’s agile project management tool is a full-featured product that is ready to use to start managing software projects, out of the box. This application is included, at no additional cost, as an installable app with the Ruly platform.

The all-in-one dashboard

There is no reason to go anywhere else. Stories, bugs, sprints, releases, charts: it’s all here on the home dashboard. Drill down on charts to see the details. Open stories and bugs, or move them from one status to the next.

All of the elements on the dashboard filter automatically to what is current and important.

Use Kanban to manage sprint tasks

Use the Kanban view to create, edit and view stories, or drag and drop them to other columns.

Get daily updates on sprint progress

Managing a sprint means keeping an eye on sprint progress and taking action before targets are missed.  Monitoring status daily is the only way to manage effectively — it can’t wait until the sprint retrospective.

The Sprint Burndown chart is a great tool to visualize how work is progressing. Targets are created automatically as stories are added to the sprint, and then as stories are moved to Done, the progress is updated as well.

The Sprint Progress chart is another perspective of the same data. This chart adds a third dimension: the number of story points that are in the QA or testing phase and are not fully done. 

Both charts appear on the Dashboard, for everyone to see, and are updated automatically as stories move through the sprint. Using no code, both charts can be easily tailored to match a different process.

Manage workflow using Alerts

Using Ruly’s built in subscription feature, users can subscribe to a story, and then get notified whenever there is a change or update to that story, or when a new comment has been added. Notifications can be sent through email, or as application Alerts that are visible in the bell icon in the top status bar.

Give Visibility to Productivity

Although the output of agile teams is supposed to be linked to the team vs the individual effort, it can be beneficial to see each developer’s output as well. The Sprint Points by Developer chart shows how each developer is progressing with the stories they are working on.

The Project Points by Developer chart shows the output for the entire duration of the project.

Manage multiple projects

There are no limits to the number of active projects that can be managed at the same time. Use the Project screen to add new ones or view and edit existing ones.

The Project screen lets you set up or edit project parameters such as default sprint length in days, or set an overall budget for the project and then see how much has been used to date. 

Note that the tabs on this screen give you access to all data on the project, in one place:

  • Stories
  • Bugs
  • Sprints
  • Sprint Progress records

Close a sprint

Once a sprint is completed, the Create Release button will close and lock the current sprint and move any undone stories to the next sprint. The dashboard will clear out the completed items, and return to showing what is currently active right now.

How this was built

The screens themselves are pretty easy to build in Ruly. Screens are generated automatically when you create data models, and then you only need to drag and drop elements around to get them in the right order. There are fewer choices in Ruly as to how screens are designed, which can be a limitation in some use cases, but it definitely makes it much quicker with fewer decisions to make.

Screens are also automatically responsive and adapt to different screen sizes, without any additional configuration.

Kanban screens are generated from list screens simply by selecting a pivot field. In the kanban example above that is used to manage stories, it pivots off the story status field (To Do, In Progress, etc. ).

Most of the work is spent on creating the rules and operations that control the logical flow of the application. There are about 30 rules and 50 operations that make up this application. These control features such as hiding and displaying fields and buttons on forms, depending on what status the record is in. They are also used to perform calculations.

Here is an example of a simple rule that controls locking a sprint once it is closed.

To get a free trial edition of Ruly and see this agile project management application in action sign up here.