Ask the Experts: Constraints, Bottlenecks, and Jira Align

[Mark Cruth]

We here at Atlassian love to help our customers solve real business problems with our products. As a member of the Solutions Architecture team, my teammates and I spend most of our time working 1:1 with customers talking about business problems and then reaching into our toolbox of Atlassian products to determine what the best tool for the job would be. Recently I was talking with @Jacques van den Berg about how concepts like bottlenecks and constraints impact the flow of work, including ways to help reveal and manage these aspects of flow using Jira Align. We then realized this would be an awesome vlog (video blog) we could do for the community!

Check out the first Ask the Experts vlog below that captures our conversation about constraints and bottlenecks, the theories around them, and how Jira Align can help you manage these in your organization. Afterwords, throw your thoughts on this discussion thread below...what are your opinions / questions / ideas on this topic? Looking forward to going deeper on this topic with everyone!

[Mark Cruth]

As promised in the video, here are a couple of those link:

Theory of Contraints: https://www.leanproduction.com/theory-of-constraints/

Little's Law: https://toggl.com/track/littles-law/

What did you all think of the conversation? Where do you see constraints and bottlenecks appear in your organization? What questions are still lingering for you?

[Fabian Lim]

Hi @Mark Cruth

Thanks for the article. Is there a sandbox environment where customers can actually try jira align features?

[Mark Cruth]

Hi @Fabian Lim ! If your company has Jira Align set up already, I'd recommend reaching out to your Jira Align admin to see if you can get access to a test environment to play with these features. If you don't have access to Jira Align yet, then I would recommend signing up for a demo instance to try it out. Go to the following link to sign up: https://www.atlassian.com/whitepapers/launchpad

[Fabian Lim]

Thanks @Mark Cruth