Darrell DuMondSr Program Manager| Princess Cruise Lines LtdSimi Valley, Ca, United States
Hello, I am moving our production team to Scrumban, using JIRA, and have a question. I want to create a board that encompasses all of our processes in order to have a full team view of the work being done. This is from project conception to deployment. For the purposes of this discussion let's say I need Ready to Work, WIP, and Completed columns for our Business Analysts, Architects, Developers, QA team, UAT team, and Deployment team. This is something like 18 columns at a minimum. It seems it may be difficult to manage but would like to hear others suggestions or experiences.
I have thought of making a separate JIRA board for each team but that would defeat the purpose of elevating the view of the entire process.
Would love to get the thoughts from those experienced with Scrumban. Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Definitely want to keep it as simple as possible.
Physical board: Color-code per role, then just have the 3 columns.
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Why Overcook?
It's still simple to manage work within sprints with fewer swim-lanes.
In my experience I have only worked with 5-6 Swim Lanes in JIRA
1) To Do [for the sprint]
2) IN Progress [Being worked on , no matter which persona is doing the work, Vendor or Development Team , Analyst or Architect]
3) Testing/Validation [ QA and UAT team]
4) Pending Customer Acceptance/Sign off
5) Deployed [note:- can be the same as done, depends on team consensus]
6) Done
7) Blocked Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
My recommendation is keep it simple. Is not about Scrumban (I hate this term) is about Kanban. If you really want to create a culture that could help about to gain into agility let the people take their own accountability. Use three columns is the best. If not, remember that people are aware in one sight 7+-2 levels. At the end, the question the team must ask themself is: which is the value? When you add columns then you are trying to return to gantt charts. Saving Changes...
You can take an overall value stream and decompose it into multiple separate Kanban/Scrumban boards. If you are ensuring entry & exit criteria are explicit, then whether it is one board or multiple boards doesn't matter.
Certain tools will allow you to aggregate/roll up content from multiple boards into a single overall view for use as an information radiator.
I'd also suggest that while your current work process is linear, you may wish to (over time) look at moving from individual work to true teaming which would reduce the number of stages a work item goes through.
Kiron
...
1 reply by Darrell DuMond
Jan 21, 2020 12:16 PM
Darrell DuMond
...
Hi Kiron,
The separate boards is what I am leaning towards. My issue is that we have 6 teams that touch a project from inception to deployment. (Deployment meaning we need to roll out the update to various locations globally and it is managed by a separate Deployment team)
My upper mgmt is keen on using Scrumban for its ability to foster a continuous improvement environment for the teams and to elevate the visibility across all teams working on a single project. Since Scrumban can manage a system of systems it's our ideal choice. Unfortunately I am stuck using JIRA due to corporate politics so I don't have much leeway to use other products.
I'll go with multiple boards to start and maybe if it's successful merging them later might provide a better holistic view.
Thanks for your advice.
Saving Changes...
Darrell DuMondSr Program Manager| Princess Cruise Lines LtdSimi Valley, Ca, United States
Jan 21, 2020 7:20 AM
Replying to Kiron Bondale
...
Darrell -
You can take an overall value stream and decompose it into multiple separate Kanban/Scrumban boards. If you are ensuring entry & exit criteria are explicit, then whether it is one board or multiple boards doesn't matter.
Certain tools will allow you to aggregate/roll up content from multiple boards into a single overall view for use as an information radiator.
I'd also suggest that while your current work process is linear, you may wish to (over time) look at moving from individual work to true teaming which would reduce the number of stages a work item goes through.
Kiron
Hi Kiron,
The separate boards is what I am leaning towards. My issue is that we have 6 teams that touch a project from inception to deployment. (Deployment meaning we need to roll out the update to various locations globally and it is managed by a separate Deployment team)
My upper mgmt is keen on using Scrumban for its ability to foster a continuous improvement environment for the teams and to elevate the visibility across all teams working on a single project. Since Scrumban can manage a system of systems it's our ideal choice. Unfortunately I am stuck using JIRA due to corporate politics so I don't have much leeway to use other products.
I'll go with multiple boards to start and maybe if it's successful merging them later might provide a better holistic view.
Thanks for your advice.
...
1 reply by Kiron Bondale
Jan 21, 2020 2:50 PM
Kiron Bondale
...
JIRA is unfortunately limited as a Kanban or Scrumban tool both from an aggregation perspective but also from a reporting perspective. Have you investigated the JIRA portfolio add-in to see if that will do what you are looking for?
If your policies relax at some point you could look at Leankit or one of the other Kanban-focused solutions out there.
The separate boards is what I am leaning towards. My issue is that we have 6 teams that touch a project from inception to deployment. (Deployment meaning we need to roll out the update to various locations globally and it is managed by a separate Deployment team)
My upper mgmt is keen on using Scrumban for its ability to foster a continuous improvement environment for the teams and to elevate the visibility across all teams working on a single project. Since Scrumban can manage a system of systems it's our ideal choice. Unfortunately I am stuck using JIRA due to corporate politics so I don't have much leeway to use other products.
I'll go with multiple boards to start and maybe if it's successful merging them later might provide a better holistic view.
Thanks for your advice.
JIRA is unfortunately limited as a Kanban or Scrumban tool both from an aggregation perspective but also from a reporting perspective. Have you investigated the JIRA portfolio add-in to see if that will do what you are looking for?
If your policies relax at some point you could look at Leankit or one of the other Kanban-focused solutions out there.
Kiron Saving Changes...
Wade HarshmanScrum Master| GDITIndianapolis, In, United States
Just an aside, since we're using the word "scrumban":
Kanban is inherently a "pull" system. On a true Kanban board, cards are pulled from one column to the next, not pushed to the next person in line. If you want to design this into your board, you may need additional columns, or (depending on your work flow) you might need to split your basic columns into "Doing" and "Done." For example, I have one team that has a Development column that is split; when development is "Done," then it can be pulled into Testing when someone has the time to do it.
I'm not telling anyone how to build your boards, it's just something to consider. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Your teams should be consolidated into one board. That's the only for everyone to make sure all the teams are aligned on the priorities. Saving Changes...
