For almost three years, I was responsible for managing the huge website TIM Portals, leading a multidisciplinary team of 29 professionals, including Scrum Masters, UX Designers, UX Writers, Frontend and Backend Developers, and DevOps, divided into 6 agile squads.

The entire operation running with agile methodology, managed through KanBan boards in Jira, with planning ceremonies, storypoints based on Planning Poke, daily-meetings, retrospectives operated with EasyRetro.

Among the activities were the evolution of the Design System, with almost 70 components, navigation flows, module implementation, component development, and integration of the Drupal Platform with various TIM internal services and applications, improvements related to performance, usability, SEO, orchestration of backups and deployment processes in Acquia Environment, and content updates.

Last year, our 12-month report demonstrated that we delivered above what was foreseen in the contract, which on an annual average represented 33% of operational optimization.

Main Products

But not limited to:

• Websites and web applications (logged in and not logged in) - with an average of over 11 million sessions per month.

• Digital solutions.

Assumptions

• Certified professionals in Acquia* to technologically operate the current CMS Platform.

• The scope of the contract includes resources focused on development, content maintenance, and monitoring and acting on the operation of the TIM website.

Activity Volume

The volume of demands performed revolves around:

• 315 stories/month;

• 1060 story points (Fibonacci sequence).

* Certified ScrumMaster® (CSM) or Kanban System Design (KMP I);
** Experience with SEO tools (e.g., Semrush, Google Search Console);
*** Professional with ACQUIA CERTIFIED CLOUD PLATFORM PRO certification or equivalent.

Agile Coach

Responsible for the correct implementation of the agility model within the partner, respecting the precepts of the agile framework used by the team. Coordinates the organization and alignment of teams in established Squads with the client and ensures maximum occupation of the minimum necessary roles.

Scrum Masters

Responsible for organizing ceremonies and evolving the agile model within the squads. A servant leader, monitors and ensures the progress of the process and the performance of the teams by facilitating their relationship and information flow.

Product Design Manager

Responsible for the final quality of design solutions, ensuring the creation of experiences according to the TIM brand's Design System, standardization of adopted solutions, etc. A focal point for addressing all design-related issues with TIM, working with TIM's technical design leader.

Product Designers

Responsible for the user experience of the product, based on the client's business objectives. They work on both high-level activities (such as information architecture, user research and testing) to identify opportunities for continuous improvements, as well as more granular levels (building mockups, prototypes, user journey mapping, visual design creation, etc.).

UX Writers

Responsible for creating and adapting the text used in digital products, providing a more resolved and engaging navigation within websites, applications, etc. Among the main activities, they develop the language used in the interface, adapting it in the most empathetic way to different customer profiles and the objectives of the product being worked on.

Tech Manager

Responsible for the development model (coding) adopted, the publication process, and the focal point for addressing all technology and system integration issues with TIM.

Fullstack Developers

Responsible for creating solutions and transforming them into efficient computational code that follows the best global standards, testing, and ensuring that the solutions meet the definition of done for each prioritized artifact (Stories). They play an important role in the technical feasibility assessments of solutions and in designing the best solution architecture.

DevOps

Responsible for infrastructure monitoring, incident tracking, deployment process monitoring, infrastructure updates, test automation, and deployment pipeline implementation.

Low-Code Developers

Responsible for page management and implementation of regionalized content.

Activity and Project Management System

For managing and transparently executing activities, tasks, and projects, a tool for demand/task management was used, utilized by both the team and the client to register and track progress. Initially, we worked with Jira, and later Azure DevOps was used to manage projects across the entire Digital area.

This allowed the client to have visibility and access to all stages of the workflow, with each professional in the squads operating in the tool according to their role in managing and updating activities, with hierarchy of items as per the agility model (epic, user story, tasks, and subtasks), as well as work stages on the boards.

Product Owner

Responsible for maintaining, creating, and prioritizing items in the product backlog. Specifies requirements, priorities, and additional details for backlog items.

Scrum Masters

Facilitate squad ceremonies, schedule and conduct rituals, identify and track impediments that the team may encounter during development. They must keep the squad's board updated so that the Product Owner can track the progress of demands and ensure that the team updates the status of activities. Agile coaches must extract a performance metrics report from the squads monthly, this extraction should be done transparently, and the report made available to the client.

Squad (Design/Development Team)

Accesses the user stories prioritized by the Product Owner and updates the status of activities daily so that the board reflects the actual progress of demands.

Management Routines

All squads will follow the rituals (planning, daily stand-ups, retrospective, etc.) of the agile methodology. At the end of each cycle/sprint, the agile coaches was responsible for generating a monthly executive report for managerial oversight with agile performance metrics from the squads (such as cycle time, lead time, and waiting time) with the aim of identifying bottlenecks and proposing improvements to the teams' workflow.