Category: Propsnoop

🤝 Team

Description

Issue overview: Website development – Real estate website. The main user roles are “agency” and “agent”.

Scope of work:

References:

🔗 Accesses & Useful links

  Milestones

🔎 QA Scope

Supported browsers and devices:

mobile and desktop

iPhone Safari (360px)

iPhone Safari (the bіggest)

Mac Safari (1440 px)

Mac Safari (1025px)

Mac Safari (1920 px)

Android Samsung S8 (360px)

Android Samsung (the biggest)

Windows Chrome (1440 px)

Windows Edge (1440 px) Windows

Opera (1440 px) Windows Mozilla (1440 px)

 Objective

 Success metrics

 Assumptions

 Milestones

 Requirements

 User interaction and design

 Open Questions

 Out of Scope

 Date

 Participants

 Goals

 Discussion topics

 Action items

 Decisions

 Relevant data

 Background

 Options considered

 Action items

 Outcome

Define your requirements

Confluence is the perfect place to start defining your requirements. You can use the Product requirements template to capture your requirements, then create your Jira epic and other issues right from the requirements page in Confluence.

Here’s how it works:

1. Create a Confluence page using the Product requirements template.

2. Choose the placeholder text ‘Link to Jira epic or feature‘ and choose Create new issue to create your epic in Jira.

3. Collaborate with your team to define your stories and save the page.

4. Highlight text on your requirements page and choose theCreate Jira issue link to create stories in Jira, and automatically link them to your epic.

5. Track the progress of the stories from the Confluence page or from within Jira.

The tight integration between Confluence and Jira Software means you can easily access issues from the Confluence page and see their status at a glance, and from within Jira Software you can see links to related Confluence pages. All the information you need is right there.

Manage your sprints

There’s often a lot of material in Confluence that provides useful context for your team during a sprint. These might be requirements documents, designs, tech specs, customer research and more. By linking these pages to epics, you make them easy for your team to find during the sprint.

Here’s how you can use Confluence to support your sprint from within Jira Agile:

• In Jira Software, create a Confluence page to plan your sprint. The page is created using the Meeting notes template and is automatically linked to the sprint.

• In an epic, link to useful Confluence pages, including requirements, designs, and more.

• Report on your progress to stakeholders using the Jira Report blueprint in Confluence.

• Use the Retrospective template in Confluence at the end of your sprint to take stock of what went well and not so well.

For people who work mostly in Jira Software, the integration means that useful Confluence pages are only a click away.

Your team doesn’t work in a silo, so it’s important to make it easy for anyone to find work you’re currently working on.

Use shortcuts to keep information accessible

Next time someone asks for a status update, direct them to your space. Confluence makes it easy to give other teams a window into your world.

The space shortcuts highlighted below can be critical to navigation for both your team and your entire organization. Add team’s roadmap, quarterly goals, meeting notes, important files, and decisions for easy access. You can even link to the work that’s not in Confluence like tasks that are tracked in Jira Software or Trello. The homepage gives a snapshot, and the shortcut links make it easy to dive deeper into those pages.