How to structure aspects of product

[ultimatetester]

I’m working on a product that has multiple aspects.

1. The product itself, having a frontend and backend

2. the “marketing” website, basically the website that lays out the features of the product and provides the download

3. research and marketing activities

What would be the most ideal way to replicate this in Jira? Currently the team size is 2, but I’d like to do it right the first time.

[Karim ABO HASHISH]

hi @ultimatetester 

Which Cloud product you are planning to use, JIRA Software or product discovery.

If you didn't plan it would be also helpful to explain what kind of activity your team will be performing to propose a proper Product/Solution within your context.

Awaiting your return.

Cheers,

Karim

[Abraham Brookes]

Jira is really designed around agile methodology, sprints, story points and whatnot. It's not suited to things like marketing documentation, client lists, content creation etc. If you are specifically creating custom software and operating in an agile fashion using scrums and sprints, Jira is a great tool. As soon as your usecase falls outside those bounds, do not use Jira. Use something more flexible like Trello or Clickup.

[Kevin Hanson]

All product events are time based, require planning, require refining and require people to do the work.  And no matter which layer of a product we talk about, they are all aligned to releasing features, timed to a road map  (that is agile in order to best manage achieving goals).   Why cant any of the non "writing code" outputs be included in a tool built for managing planning?  You can find all of this in Jira issue types actually.  That its easy to see how they all are working together, is another story (no pun intended) that Jira does not do so well to champion to their users.