title: How should both a core team project and individual projects be handled with JIRA and the SCRUM method?
body: <p><strong>Summary</strong></p>
  
  <p>We're a medium sized company that has a development team of five team members. We recently started learning/employing the SCRUM method to our R&amp;D department. </p>
  
  <p>Our core team has one project, while each employee has individual task and projects. Some of those individual projects are only big enough for a single developer to complete. </p>
  
  <p>Additionally, a single developer may be supporting a product they released individually. </p>
  
  <p>Furthermore, we currently use a JIRA SCRUM board to track our progress in our core team project, while we each use individual JIRA Kanban boards to handle our individual tasks/projects.</p>
  
  <p>We found that it's easy to go over the core team's project during the sprint review, but it's difficult to have visibility into our daily tasks and projects not related to the core project.</p>
  
  <p>Should we utilize a single Kanban board that pulls in all of our core teams SCRUM board issues, and all of our other non-core team tasks/projects? </p>
  
  <p>Then we go over all issues in the all-inclusive Kanban board during our sprint review meeting? If so, how should we filter our Kanban board? Updated within a certain time frame, labels, etc...?</p>
  
  <p>Or should we use a single SCRUM board and force the entire team to plan and estimate both the core team's project and all the individual tasks/projects? What happens when new support issues occur during the middle of the sprint? Do we adjust the sprint scope mid sprint?</p>
  
  <p><strong>Question</strong></p>
  
  <p>What method of grouping should we use to present both our core team's shared project, and each developer's individual tasks/projects while preserving SCRUM estimation and planning?</p>