Inspiration

At Regos Dev Studio, like many other teams in the world, we work on multiple projects at the same time. Sometimes the people work on or leads more than one project simultaneously and, with the time, the standup meetings become a pain and a lot of time is spent to attend the calls.

In addition to that initial problem we identified a few more:

  • It was not easy to see what other persons who I work within a team are doing on other teams
  • For some people it's easy for forget the issues they were or are working on while giving a status
  • By default there is no a record of the status history for a team, if needed, someone will take notes to track that history

In an internal effort to solve this situation, we decided to implement something to keep all the teams in sync, reduce the meetings count, and integrate our status with Jira by default.

What it does

Helps the teams to run async standups in Jira. The main features provided by the add-on are:

  • Allows the Jira users to run async standups integrated with Jira Cloud.
  • Ability to create multiple standups with dynamic questions and notifications on a project basis to support multi-teams projects.
    • If desired, the add-on can be disabled for specific projects.
  • Jira issue suggestions are provided to the team members while submitting the status.
  • Provides a section to see a cross-team status of the people who you share standups with.
  • Auto generates a status for those team members who haven't sent the status at a certain point in time.

How I built it

We have some experience building apps for Jira and Confluence using Node.js, ACE, and React. With the time we have developed a good code base so that we decided to use it for this project.

The work started on the UX side by building freehands and prototypes in Invision, then we went through internal usability tests to make sure we cover our internal needs (in the end this is where everything started).

Once we felt we were ready to start building the app... well the team started to code it. We decided to use Atlaskit to reuse the components that Atlassian already wrote for us and, after a couple of weeks, we had an MVP to start using it in our teams.

Honestly, the result was great and we started to see good results by implementing async standups for our teams. A side effect of starting using the add-on in an early stage was that we collected feedback as we were building it!

Finally, we did put attention to permissions and performance tuning in a way that we even created our first open-source package, but we'll talk more about that in the next sections.

Challenges I ran into

One of the challenges (and advantages at the same time) was to update the requirements based on the team's feedback and keep building the app at the same time.

Also, as we mentioned before, for some parts of the app did some performance tuning so that we ran some tests using different configurations and environments. At the same time, we were working on the open-source package needed to support the changes we wanted to implement for performance improvements.

Accomplishments that I'm proud of

We are very happy about:

  • Our team using a great tool and reduce the meetings count
  • Having a production-ready app to publish after the hackathon :D
  • We are already using our first open source repository
  • We make a great improvement in our technology and codebase thanks to this app. We are excited to start sharing our technology with the community in the near future!

What I learned

The main lesson after this event is that the quality of a product improves drastically when you and your team use it on a daily basis. Some times we are focused on building solutions for others, but it's great when you build solutions to solves problems you are already facing.

What's next for Regos Team status for Jira Cloud

A lot of things!

The first one is to make it public. We are excited to publish the add-on and see how other teams start using it and improving their work.

Also, we'd like to improve the Jira issues suggestions in the status form and enhance the auto-status generation feature for the users who haven't sent the status. With time and more data, we are planning to improve the reports to provide powerful insights for project leads.

Finally, we are thinking about future integrations with Slack and other messaging platforms to improve the notification system and the status submission.

Built With

Share this project:

Updates