Agile & Productivity Strategies

When projects follow a linear path, and the scope remains relatively stable, it becomes more straightforward to define the scope of our analysis. In such cases, we can more easily identify the parameters and variables that need to be considered, allowing for a more focused approach to our analytical process.

However, when the focus shifts from larger end-to-end projects to smaller, more incremental product blocks, the nature of the analysis fundamentally transforms. It becomes less about following a predefined set of tasks and more about embracing a mindset that is adaptable and responsive to the evolving nature of these product blocks.

This shift in perspective necessitates a change in how we approach and conduct our analysis, requiring a more dynamic and flexible mindset to effectively capture the intricacies of these smaller-scale yet significant components within the overall product landscape.

How can we discern the analysis demand in a cross-product initiative?

Multi-purpose hat

A Business Analyst plays a pivotal role in managing the diverse responsibilities associated with a product, project, or portfolio of products. Their contribution extends beyond facilitating communication between business stakeholders and technical teams, encompassing comprehensive involvement in identifying, gathering, and refining the requirements of a product. From the early stages of recognizing a business opportunity to delivering a competitive and valuable solution that leads in the market, the presence of a Business Analyst is indispensable.

BA as the bridge from Product/ Stakeholders (Business) to Development (functional)

• Analytical
• Problem Solving
• Communication skills
• Technical (Infrastructure)
• Business (Marketing,..)
• Agile framework

BA as a Business Advisor

• Cross-Product goals alignment
• Effective estimations, risks, unknowns and external dependencies

BA as the notary process

• Requirements (Use cases, User Story’s,..)
• Design baselines
• Testing standards
• Deployment phases

—

BA as a Business Coach

• POCs (Solution improvements)
• Communication efficiency
• Tools sharing
• Market competition analysis (risks, effectiveness)

What is the best approach to structuring and monitoring our analytical strategy?

I don’t have the key to success, as every company, project, team, and individual works differently. Therefore, adaptability and a well-oiled team-organizational dynamic structure are essential.

The role of Business Analyst (BA) has been devalued, especially with the rise of agile methodologies. In the past, there was no specific role for BAs in a scrum team. The responsibility for functional analysis was handled by tech leads, and the connection with stakeholders was a joint effort involving Product teams, Scrum facilitators, and Tech team leads. However, practical analysis is crucial for any initiative, particularly in iterative deliveries like agile, as it’s not just about developing valuable functional solutions but also about keeping the organization competitive in the market.

As a scrum master, agile coach, and manager, I saw how we isolated analysis. Where downstream analysts (functional development) and upstream analysts (business OKRs or KPIs) don’t merge ever for a well common. Even when they are truly dependent on each other.

We have embraced the methodologies of SoS and LeSS to elevate our Scrum management and adopted SAFe to enhance overall project management practices. We need to take the next step and unify our Product Data Management efforts across the entire organization, from top-level initiatives to operational execution. We need to envision a collaborative environment where Business Analysts take the lead, leveraging data to drive us forward.

How do we do that in an agile environment and in a tool?

Evolution requires coordination; we need to plan and adapt according to the team’s and the organization’s level of maturity. We cannot force things to happen or stay if we are not ready for them.

With a culture well adopted and routines well established any tool will fit in, but not otherwise.

Do you want to know more about habits?/ ¿Quieres saber más sobre hábitos?

Get to know us!/ Conócenos!