Improved burnup graphics display performance.
Product burnup more accurately represents product history.
The graph displays the entire sprint duration and shows the sprint scope. The global scope has been removed so as not to disturb the reading of the graph. A guide has been added to follow the progress of the sprint.
The file is named according to the PDF title.
Export preferences are saved and reused for subsequent exports.
The file is automatically named according to the product name.
The background tasks indicator displays the number of new events since the last consultation.
Added the ability to search for values in filters.
Ability to invite several new users and improved interface.
Product dashboard graphics have been improved. A product burnup graphic has been added and the sprint graph can now be set to burnup instead of burndown. Burnup graphs can be set to choose the unit measured (number of items or ratings) and the duration and unit of the history (days, months, sprint).
Item search by reference now also works without prefix. When applicable, items from the same project are prioritized.
By default, the latest modified items from the same project are presented first.
It is now possible to open the list of items from a kanban or product backlog column.
Sub-items and evaluations can now be printed or not.
Ability to define exported columns.
Improved XLSX export formatting.
A new feature for printing backlog elements is now available. It allows you to select backlog elements and generate a PDF. Document preparation is performed as a background task.
It is now possible to create backlog items from storymap items.
When a backlog item is moved to "to do" status and an active sprint exists, Optera automatically places the item in the sprint.
A search by name has been added to account management.
Improved ask estimate option to take backlog sub-elements into account.
More understandable worklog display on backlog items.
A new option lets you move a backlog item to another product directly from the backlog item page or modal.
Added an edit button to enable editing of the backlog item description.
The export and print options are automatically disabled if the number of selected elements exceeds the maximum allowed.
A message informs of the end of a background job.
When the sprint is closed, unfinished items that return to the product backlog are placed in first place.
Optera now offers a global search from the search bar. This allows you to search not only for items, but also for products and organizations. This search enables rapid navigation between projects and items.
]]>Two-factor authentication with OTP. Compatible with mobile OTP applications such as FreeOTP or GoogleAuthenticator.
Do story mapping in Optera. Create story maps for your entire product or a specific set of features.
Manage time budgets on time entry accounts and alert when a configurable threshold is exceeded.
Improved tag field for simplified entry.
The product list allow to archive products no longer in use. Filters can be used to display archived products. A product search by name has also been added.
Authentication required when changing email address.
Backlog items in a Kanban column can now be easily exported.
Improved Excel export columns format.
Optera.io now tries to automatically reconnect websockets in the event of disconnection. If the error persists (e.g. due to network connection problems), it is displayed to the user with a button to reconnect.
You must now have “Account manager” or “Organization manager” rights to modify time tracking clients and accounts.
Small improvement in navigation for unauthenticated users.
A new item export function is now available. It allows you to select backlog items and export them in CSV and XLSX (Excel) formats. The export is performed as a background task.
When the user closes a background job or marks a notification as read, it is also closed or read in other tabs and browser windows.
Functionality for exporting the list of completed backlog items in a release.
If websockets used to refresh kanbans, background task status and notifications are disconnected, an alert is displayed to the user with a button to re-establish the connection.
Parent backlog items show the number of backlog sub-items still open in addition to the total number.
Improved pagination on mobile devices.
A new filter allows you to list only parents and independent backlog items, or only sub-backlog items.
Improved user dashboard performance.
Background tasks are now displayed next to notifications. They indicate their status and give access to task error messages if any.
A summary is displayed on completed jobs.
Completed jobs (successful or error) can be deleted by the user.
It is now possible to update several items of a product from the item search screen. Updating takes place in the background.
The following fields can be modified:
The bulk update feature (OPT-86) is also available for an entire Kanban or Product Backlog column.
Option to disable notifications during a bulk update.
It is now possible to move items to other products. When moving, the user must indicate the corresponding type in the destination project for each type. The same applies to epics.
Optera is now a progressive web app. It can be "installed" on a tablet or smartphone. The application uses PWA functionalities to cache its components. However, it cannot be used offline.
In addition to internal notifications, Optera now offers the option of receiving desktop and email notifications. For each type of notification, users can choose which channel they prefer.
Filters now propose an empty value when the field can be empty.
It is now possible to create links between items from different products within the same organization.
The user can now choose the size of lists.
Backlog sub-items can be reordered to present them in a logical order. This order is resumed when the item is set to "to do".
Internal notifications are refreshed via a websocket connection.
Assignment, mention and team welcome notifications are no longer sent are no longer sent during Jira imports. All notifications are disabled in bulk updates.
When a backlog item is closed without passing through the "done" status, a popin asks for the resolution code (done, will not be done, impossible to reproduce, duplicate).
If the modal of the backlog item being edited is closed, Optera now asks for confirmation.
The personal dashboard shows the items assigned to the user. A button displays all items concerned.
The user can customize the columns on backlog item lists.
Various visual enhancements, including filters and pagination.
The user can filter the Kanban with tags.
Worklogs can be filtered by product.
Switch between light and dark mode from the user interface.
archived accounts have an archived flag instead of a checkbox.
Improved list performance, especially on dashboards.
Accounts are hidden as they are added to a product in the product account settings screen.
Add a delay field to backlog items.
Pre-backlog values are hidden when selecting status on current backlog items (to do, in progress, done).
Mentions are now handled in such a way as to avoid duplication. The system only considers a mention if it has been added since the previous state of the description or comment field, rather than any mention added.
A popin now displays some useful information about the application. In particular, the version of the API and the application used.
Allows product admin to deactivate backlog in simple cases where Kanban is sufficient.
Displays merge requests, CI build jobs and commits on the item. See documentation.
Import your items from a Jira project.See documentation
Retrieve summary information when you mention a ticket in slack.See documentation
Allows you to restrict the number of accounts available on a product.When a user enters an account on a work log,he/she can then only select it from the predefined accounts.
Preparation of a background task system for use with Jira imports and in anticipation of tasks to be developed in a later release. Automatic cleanup of completed jobs.
Daily Scrum meetings must respect a well-defined basic structure to remain effective. The meeting must be short (generally limited to 15 minutes) and take place in the same place at the same time every day. Each team member will answer three key questions: What have I accomplished since the last meeting? What do I plan to accomplish between now and the next meeting? What obstacles or problems have I encountered or anticipated? Respecting this structure will keep the meeting concise and focused on essential information.
Daily Scrum meetings should be a space of transparency where each team member openly shares their progress, challenges and needs. It's essential to foster an environment where team members feel comfortable sharing honestly and where problems can be identified quickly. Encourage mutual trust and ensure that all team members have the opportunity to express themselves freely.
Daily Scrum meetings are not about solving complex technical problems. Rather, they are an opportunity to briefly share task progress and identify potential obstacles. Avoid getting lost in technical details during the meeting. If issues require more in-depth discussion, schedule separate discussions outside the meeting to avoid slowing down daily progress.
Team members must be fully engaged at Daily Scrum meetings. Make sure all members are present at the meeting and fully focused on the exchanges. This also means being punctual and keeping to the time allotted for the meeting. By maintaining a strong commitment, Daily Scrum meetings will become a consistent and effective ritual for the team.
To facilitate understanding of task progress, we recommend using a visual chart or a tracking tool such as a Kanban. These tools enable the team to quickly visualize tasks in progress, completed tasks and obstacles encountered. This facilitates communication during Daily Scrum meetings and enables everyone to quickly understand the overall state of the sprint.
Obstacles and problems identified during Daily Scrum should be dealt with proactively. Encourage the team to find solutions quickly and take the necessary steps to overcome obstacles. By encouraging a proactive approach to problem solving, the team can maintain positive momentum and avoid delays.
Daily Scrums are a key element of the Scrum methodology, enabling the team to synchronize on a daily basis and quickly detect obstacles. By following these few rules, you can optimize team collaboration and maximize the effectiveness of these daily meetings. By respecting the basic structure, promoting transparency, avoiding excessive technical detail, keeping the team engaged, using visual tools and encouraging the proactive resolution of obstacles, you can create an environment conducive to the success of your Daily Scrum and the efficient advancement of your product.
]]>Scrum is an agile project management framework that emphasizes collaboration, adaptation and continuous delivery of high-value products. It is based on the principle of dividing a project into iterations called "sprints". Each sprint is a fixed period of time (usually two to four weeks) during which part of the work is accomplished.
The Scrum team is made up of members who work together to develop and deliver the product. The team is self-organized and responsible for the realization of functionalities. It includes professionals with the skills needed to design, develop, test and deliver the product. The team works closely with stakeholders. Scrum defines 3 roles:
Developers: Developers are the members of the Scrum team who are responsible for getting the job done.
Product Owner: The Product Owner represents the interests of customers and users. He or she is responsible for defining the product vision, managing the Product Backlog and making decisions on the features to be developed. The Product Owner works closely with the development team to understand stakeholder needs and prioritize Product Backlog items. He ensures clear communication between the Scrum team and stakeholders, and is responsible for maximizing the value delivered by the product.
Scrum Master : The Scrum Master is responsible for facilitating the Scrum process and ensuring that the team adheres to Scrum principles and rules. The Scrum Master helps to eliminate obstacles that may hinder the team's progress, promotes effective communication and facilitates problem-solving. He acts as a coach and facilitator for the team, keeping them focused and productive.
Working together, the developers, Product Owner and Scrum Master collaborate to maximize the value delivered to users and adapt iteratively throughout the development process.
Scrum defines three artifacts for organizing and tracking product work:
The Product Backlog: this is the ordered list of features, enhancements and fixes that need to be implemented. The Product Owner is responsible for managing the backlog and its evolution over time. He or she works closely with stakeholders to ensure that the backlog accurately represents the product's needs and priorities.
The Sprint Backlog: this is the list of tasks to be accomplished during a specific sprint. The development team selects items from the Product Backlog that they can complete during the sprint, and adds them to the Sprint Backlog. The Sprint Backlog is usually created at the sprint planning meeting, where the team breaks down features into smaller tasks and estimates the effort required to complete them.
Increment: This is the result of work carried out during a sprint. It is a functional version of the product that integrates all the features developed and tested during the sprint. At the end of each sprint, the increment must be potentially deliverable, meaning that it is in a production state and can be deployed to users or stakeholders.
Scrum provides for regular events to facilitate collaboration and transparency:
The Sprint: The Sprint is a defined, fixed period of time during which the development team works to deliver an Increment of the product. The typical duration of a sprint is two to four weeks, but this can vary according to the needs of the team and the project. In principle, during a sprint, no changes are made to the objectives and selected elements, allowing the team to concentrate on completing the planned work.
Sprint planning: this is a meeting at which the development team and the Product Owner define the sprint objectives and select the backlog items to be implemented. The team also estimates the effort required for each task to create the Sprint Backlog.
The Daily Scrum: this is a daily 15-minute meeting where each team member shares what they have accomplished since the last meeting, what they plan to do next, and whether they are encountering any obstacles. This meeting enables the team to synchronize its activities and quickly detect any problems.
Sprint Review: at the end of each sprint, the team presents the completed functionalities and solicits feedback from the Product Owner and stakeholders. This is an opportunity to gather feedback from users and make decisions on improvements to be made to the product.
Sprint retrospective: this is a meeting where the team reflects on what went well and what can be improved for future sprints. It enables the team to take corrective action and learn from experience, to make the team more efficient and productive.
Scrum is a powerful project management framework that offers greater flexibility, transparency and collaboration. By following Scrum's principles and rules, teams can better respond to change, deliver high-quality products and create added value for their customers. It should be noted that the Scrum framework can be adjusted and adapted to the specific needs of each team and project.
Although not mandatory, the use of specialized tools can facilitate the implementation of Scrum. Optera.io, for example, is a software package offering features dedicated to product development in Scrum mode. It manages backlogs, tasks and sprints, visualizes progress with intuitive dashboards, and facilitates collaboration between team members. By using Optera.io, teams can optimize their Scrum practice.
Scrum also encourages team self-organization and fosters a culture of continuous improvement. Team members are empowered and actively involved in the decision-making process. Regular meetings such as the Daily Scrum, Sprint Review and Sprint Retrospective enable the team to share progress, gather user feedback and reflect on improvements for future sprints.
If you want to improve project management in your organization, Scrum could be the framework for you. Give it a try and discover how it can transform the way you work, improve your team's efficiency and lead to outstanding results. By embracing Scrum and exploiting the benefits it offers, you can move your projects forward in an agile way and successfully achieve your goals.
]]>