Project setup for Marketing, Development, Sales, etc...

Hello all,

I was wondering if there was a best practice to this type of configuration. I have a project (Test Project), I have an Agile Scrum board for development tasks. I want to be able to tie another board for our marketing team to use that is tied to the same project. Is this bad form? Are you supposed to create a new project for each team? For instance Test Project Development, Test Project Marketing, etc...? I am treating the project as the Product which will have each of these departments.

Any advice is appreciated!

2 answers

1 accepted

Hey Trent.

As the Scrum board is a board of tasks that should be done in a sprint, if your development team and marketing team are not doing concurrent tasks of that same sprint you will prefer to separate them in two projects (or at least two different sprints).


Actually this will greatly depend on what's your project like.

For example if your marketing team will make a campaing for the product created by your development team, this will be done on, at least, a separeted sprint ( I would prefer to use a separated project). If that marketing team will not interact with the development you should be safer create two projects.

hope this helps.

This does help. So you're saying I can't set it up like:

Company:

  • Project One
    • Marketing Board
    • Sales Board
    • SCRUM Board
  • Project Two
    • Marketing Board
    • Sales Board
    • SCRUM Board

For each project we could have different teams for marketing, sales, and development. So it would be nice to have this type of navigation. Does that make sense?

Hey Trent.

As the Scrum board is a board of tasks that should be done in a sprint, if your development team and marketing team are not doing concurrent tasks of that same sprint you will prefer to separate them in two projects (or at least two different sprints).


Actually this will greatly depend on what's your project like.

For example if your marketing team will make a campaing for the product created by your development team, this will be done on, at least, a separeted sprint ( I would prefer to use a separated project). If that marketing team will not interact with the development you should be safer create two projects.

hope this helps.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

12,063 views 15 13
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you