Act full transparency
0 likes148 views
This document discusses how tool integrations can help development teams better align their technical work with business priorities through semantic integration. It describes how current tool integrations are often only technical in nature, providing links between tools but not helping understand relationships. Semantic integration as provided by Sellegi ACT builds bridges between isolated information across tools. This allows Sellegi ACT to actively detect risks, errors, and potential delays before they occur by understanding dependencies across data from multiple tools. As an example, semantic integration could detect if rescheduling a work item in one tool impacts the product roadmap in another.
![Page 2 (2)
The daily re-planning business as an example
As soon as plans are made or changed Sellegi ACT highlights risks, errors and conflicts
according to a multitude of semantic rules. These rules use data and dependencies across
information from all involved tools and can detect possible conflicts between information only
coupled loosely and indirectly.
For example, a team needs to re-schedule a seemingly unimportant work item (Admin UI) from
the next sprint to a later one
Since the roadmap
planning is done in a
completely different tool
this conflict could easily
have been missed.
Another common source
for problems is that the
distribution of work to the
teams not always follows
the business priorities.
As a consequence the planning of the work in distributed teams can become inconsistent with
each other and out of sync with the roadmap.
Semantic integration in Sellegi ACT will enable you to
*)
Have a product road-mapping capability with real-time consistency control to development data
Get immediate feedback if your plan conflicts with business or project priorities
Access information from various sources in one visual project information central
Provide a common vision for all teams and improve stakeholder communication
Have traceability from business requirements to developed products
Minimize waste by identifying parallel development opportunities while avoiding collisions
Use drag and drop planning for different aspects of your project from a release perspective
Spend less time on investigations
According to Wikipedia semantic integration “ is the process of interrelating information from diverse sources […],
documents of all sorts […]. In this regard, semantics focuses on the organization of and action upon information by
acting as a mediary between heterogeneous data sources which may conflict not only by structure but also context
or value.”](https://image.slidesharecdn.com/actfulltransparency-131106142155-phpapp01/85/Act-full-transparency-2-320.jpg)
Act full transparency
- 1. Full transparency for agility at scale How often is the realization of technical work unaligned with business priorities and roadmaps? What would happen if developers could get immediate insight into their contribution to the business value? Moreover what would happen if they got instant feedback when their technical work becomes unaligned with the business priorities? Agile development is made for change. In order to work, the decisions and authority has to be delegated to the people impacted most by these decisions. That means that the development teams have to be able to prioritize and select which work to do next. It does not mean that the teams can choose freely without constraint. The selections have to be made within the frame of the business needs and priorities. Often the development teams lack efficient insight into the business impact of their decisions. At the same time management often lacks insight into the consequences of decisions made on the technical plane. This lack of insights leads to a late discovery of potential risks, delays and unnecessary work. Tool integrations can help A lot of tools within the agile planning and development domain are tightly integrated with each other. Unfortunately these integrations are mostly of a pure technical nature. As a consequence a team might have links to all related planning items available when selecting which user story to delay in the current increment. The information is there. It is available as links, mentions of IDs for elements in other tools and similar means. Often this information is there, but you brain will only hold 7 things in focus at one time. The information is not looked up, followed or understood. Effectively this information is not acted up. Identify hidden risks and address them proactively Sellegi ACT is not a tool relying on technical integrations only. Sellegi ACT provides semantic integration*) of tools used in the agile enterprise and within agile lifecycle management. It builds bridges between islands of isolated information. Sellegi ACT integrates tools from all domains expressed in the Scaled Agile Framework (SAFe). As a consequence Sellegi ACT can understand and actively detect numerous risks, errors and possible delays in the plan before they happen.
- 2. Page 2 (2) The daily re-planning business as an example As soon as plans are made or changed Sellegi ACT highlights risks, errors and conflicts according to a multitude of semantic rules. These rules use data and dependencies across information from all involved tools and can detect possible conflicts between information only coupled loosely and indirectly. For example, a team needs to re-schedule a seemingly unimportant work item (Admin UI) from the next sprint to a later one Since the roadmap planning is done in a completely different tool this conflict could easily have been missed. Another common source for problems is that the distribution of work to the teams not always follows the business priorities. As a consequence the planning of the work in distributed teams can become inconsistent with each other and out of sync with the roadmap. Semantic integration in Sellegi ACT will enable you to *) Have a product road-mapping capability with real-time consistency control to development data Get immediate feedback if your plan conflicts with business or project priorities Access information from various sources in one visual project information central Provide a common vision for all teams and improve stakeholder communication Have traceability from business requirements to developed products Minimize waste by identifying parallel development opportunities while avoiding collisions Use drag and drop planning for different aspects of your project from a release perspective Spend less time on investigations According to Wikipedia semantic integration “ is the process of interrelating information from diverse sources […], documents of all sorts […]. In this regard, semantics focuses on the organization of and action upon information by acting as a mediary between heterogeneous data sources which may conflict not only by structure but also context or value.”