Agile Hive vs. SiteVision

Agile Hive is used for our value train
within a SAFe setup. Every quarter we organize a so-called Product Increment
(PI) Planning, where we plan all Features and Enablers in Agile Hive.
Based on the priority of the Product Manager all teams plan their Features and
Enablers accordingly to the sprints that are determined by the Release Train
Engineer and set up in Agile Hive. The teams then create User Stories and
estimate them and based on their sprint velocity (defined in Agile Hive)
Product Owners can see how many Features and Enablers are realistic in one
quarter (Product Increment). Further, dependencies across teams can be defined
and made visible in Agile Hive, so that the plan is feasible. Without Agile
Hive it would be hard or impossible to plan across several teams within a value
train and to manage all dependencies. Additionally, with Agile Hive the plan is
more realistic, so what can be achieved within one quarter in product
development.

Incentivized

well suited scenarios are : 1. In terms of architectural context its well suited to know the exact location by 3D Model approach. 2. Its excellent to use in civil construction firms to get the exact distance management approach and to get the best design approach. Less appropriate: 1. For those projects which are not outside or in outdoors its less suited to use there. 2. AR technology +3D tech could be seen in the areas having great land coverage

Incentivized

• Roadmapping in terms of defining epics and planning them across a timeline and across teams.
• Showing dependencies within teams and across teams and over time horizon.
• Create transparency throughout the product organization and teams about what is planned.

• Get the exact AR version of the project site
• Helps in distance management on the site by measuring the spatial points.
• Helps in power management too.

Incentivized

• I believe the training and support could be more hands on and easier.
• The Agile Hive - SAFe in Jira product can be a bit robust to understand.
• Having Knowledge transfer videos can help more than documentations.

Incentivized

• cloud services could be improved much.
• accuracy could be enhanced for the hardware tools like GNSS
• The AR technology could be mixed with the other latest updates to make the system more efficient and light.

Incentivized

It has in general a good usability, but there are some downsides, the big picture view of the entire product increment is too static, so there is no zoom in or zoom out. Mostly throughout planning it is necessary to zoom in to a sprint level and manage the user stories there. Also, the pig picture view has some limitations, because you cannot read the entire user story name (boxes are too small).

Incentivized

With Jira Software alone it is also possible to plan a SAFe product increment planning, but it would be nearly impossible to see the overall big picture of all product teams involved in a release train. So, the planning on sprint level for one team would be more efficient, but the planning for a whole quarter with all dependencies across teams would be not feasible to present. Therefore, Agile SAFe enables value trains an efficient way to plan a product increment.

Incentivized

1. Easy to use 2. Easy to accessible from play store 3. Clarity of the apps shown in the screen. 4. Help center is very helpful. 5. Accuracy is very good as compare to other apps. 6. Distance management and AR tech mix up is really appreciable. 7. Power management is nice add on feature

Incentivized

• More transparency.
• Better product decisions.
• Saving time and resources.
• Less critical dependencies.

• got the clear contextual clarity of the site
• Exact augmented points are there so that spatial data could be more enhanced.
• power management is an excellent approach which has a greater impact on the project.

Incentivized