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?
...
1 reply by Rami Kaibni
Mar 08, 2018 10:23 AM
Rami Kaibni
...
Got it, I think Andrew did not leave any room for me to contribute but I am curious to know something: Do you believe one app can do it all ?
Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
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
etc....
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.
...
1 reply by Sante Delle-Vergini, PhD
Mar 08, 2018 4:47 PM
Sante Delle-Vergini, PhD
...
Great list Andrew, there are some things I didn't think of. I like making non-ready stories invisible; perhaps a toggle switch.
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).
Kiron
...
1 reply by Sante Delle-Vergini, PhD
Mar 08, 2018 4:51 PM
Sante Delle-Vergini, PhD
...
Thanks Kiron, I saw some apps have something along the lines of a roadmap, but not sure about the traceability from vision to roadmap to release. Good points.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Mar 08, 2018 3:51 AM
Replying to Sante Delle-Vergini, PhD
...
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?
Got it, I think Andrew did not leave any room for me to contribute but I am curious to know something: Do you believe one app can do it all ?
...
3 replies by Drew Craig, Kiron Bondale, and Sante Delle-Vergini, PhD
Mar 08, 2018 10:38 AM
Kiron Bondale
...
One Tool to rule them all, One Tool to find them (stories), One Tool to bring them all, and in the agile chaos bind them
Mar 08, 2018 11:00 AM
Drew Craig
...
One of the benefits of Atlassian's JIRA. The add-ons available for organizations to piece-meal a solution to suit their needs.
Mar 08, 2018 4:52 PM
Sante Delle-Vergini, PhD
...
Ah that's the holy grail Rami. I think any great (lightweight) Scrum app will still need to include options for things like Kanban Boards etc like Kiron mentioned.
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
etc....
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.
Great list Andrew, there are some things I didn't think of. I like making non-ready stories invisible; perhaps a toggle switch. Saving Changes...
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).
Kiron
Thanks Kiron, I saw some apps have something along the lines of a roadmap, but not sure about the traceability from vision to roadmap to release. Good points. Saving Changes...
Got it, I think Andrew did not leave any room for me to contribute but I am curious to know something: Do you believe one app can do it all ?
Ah that's the holy grail Rami. I think any great (lightweight) Scrum app will still need to include options for things like Kanban Boards etc like Kiron mentioned. Saving Changes...
"If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas."