Hey, the idea of a project poster is pretty neat. But I wonder where Atlassian does the actual work of 'creating' the project with all its facettes.
You define the problem
You envsion a solution
You validate assumptions and answer questions
Everything happens on a project poster, you may also create an experience canvas and a user journey. But where does the actual creation of the project with its features happens? I am talking about texts, button labels, what for emails are sent out to which user after which action, edge cases etc.
Does this execution happens in JIRA? How does it look like (in a really specific manner)? Because we have problems getting it right using Confluence and JIRA in combination. Esepcially using JIRA tickets with its fields in a good way.
Hi Lars! I can't speak to our software projects (hoping someone else can chime in on that), but for marketing and many other projects, a LOT of the work gets done in Confluence.
Of course, there are also JIRA issues that track what all needs to be done to bring the project to live (build an email, create design assets, etc) and when it needs to be done.
Typically, we add a link to all the relevant JIRA issues at the top of pages. It's a bi-directional link, which makes it easy to jump from page to issue and back again. Here's an example:
Let me know if you want more details on any of this :-)
...hinking that once instituting agile, they’re done with a process change. The idea of agile is that you're able to adapt to change and that you improve your releases over time. The same is true of the p...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events