Please login or join to subscribe to this thread
With all those letter after my name, yet, I am not very sure I fully understand your question. Can you ellaborate more Sante ? :D
lol ok, apps like Jira have pretty much all the features like a product backlog, you can add epics, stories, tasks, features, bugs, there are information radiators like burndown charts, cumulative flow diagrams, there's an Agile board of sorts where you can create a process flow of the user stories in progress etc. and a bunch of other things. But it is also very heavy because it was originally an issue tracking app (still is) and this legacy is still in the app's features and look and feel. So I was wondering if someone were to build a Scrum app from the very start, that teams could use in their projects, and it was online, what would that look like?
Thanks for clarifying.
This is a huge question. Simplicity, clean UI, open API's for integration, mobile friendly, touch screen friendly, and scalable for different types of use-cases based on what is being used (SAFe, Scaled Scrum, Scrum, etc.)
As a SM, I want ... just kidding
Definitely an easy method of creating stories
Stories are not visible on backlog until READY
Drag 'n drop to Sprint from backlog (like JIRA)
Simple method to modify kanban columns (workflow)
Discussion at all levels; Epic, Sprint, Story - with @mentions
Integrate with LDAP or AD
Simple permission allocation (defined roles - like JIRA)
Metrics/Reporting - export capability
Some traceability with ACT's and Issue tracking
Integration with WebEx/GTM for easily scheduling/starting meetings with the team
Able to create team level dashboards and expose to leadership
Full ALM, integrated with development environments and version control (git) to simplify issue tracing
Much of this is in JIRA, if not all. Atlassian really has been doing a lot of work to improve its suite of products with JIRA, GIT, Confluence and the wealth of add-ons for JIRA to integration and tools like Program Boards.
The challenge with not allowing some flexibility and scalability is that unless a team keeps their practices static (which is against the principles of inspection & adaptation), their use of such tools will evolve. For example, some teams might start with sprints & scrum boards but move to Kanban.
What would be good is a tool which supported capturing traceability from vision to roadmap to themes/epics/stories and had built-in support for common prioritization and sizing approaches (e.g. MoSCoW, WSJF, T-shirt, Estimating Poker).
Please login or join to reply