jira - Scrum user stories for rebuilding an existing web site -

I have another idea about using scraps to rebuild an existing site while maintaining certain features from the previous site . While we are still in the "rediscovery" phase of the project, I am thinking that can I include other user roles such as Content Strategist (Auditing Content), Site Builder, etc.? I know that story is careful for stories, however, can I add other user roles for project planning and assessment purposes?

That is, I am using JIRA scrum board and made epic based on stages (i.e. Google Analytics, Content Audit Phase) What will be the role of the user in these cases? Are we still collecting the requirements? Should I build sprints instead of running the sprints based on those tasks? Or should I use Kanban?

The first sentence leads me to believe that you have something to do to fit your project Under the guidance provided by Scrum, facing the mental friction,

I would also like to say that the "types of people" who are going to use your web application, usually by tight teams Individuals , then using the example above ...

"One As Sio expert ... "

SEO expert will have a personality you can have a lot of personality as an agile project. Keep it appropriate so you do not get stuck in the details which are not useful, but there is no limit.

When these roles come on project team , then that is where guidance from Scrum starts to feel like an obstacle. Shocks say that you have a SM, PO and team member. What is a Content Strategist on a Scrum Team? They can be members of a team and work (participate in speculation, distribution, planning)

They work on "user story", which they were working on, Like anybody else, they will also be done within the sprints.

Scrum (as prescribed) should be tough enough and this hardness usually causes people to pay attention to other methods such as Kanban or reduce the hardness of the team slum and they Scrum are not.

Kanban (or should I say the Kanban method says that the description by David Anderson and the University of Lancaberne are not directly in replacement from the drum. Virtual Cannbon System is a work management technique used by the Kanban method. The virtual particle system can be used by a peak team to use their board and to manage their work so that they are still available. While being disciplined, they can be allowed to expand beyond the obstacles of the drum. Using the Virtual Canaan System The Gel is Not Out of Free Cards You can become disciplined.

A virtual kernel system, corrected, will describe the process that you is required for your project, And develop it over time to continually improve Allow and be consistent with the needs of the team. This is freedom where virtual particle systems are a significant improvement over the guidance provided by Scrum. They allow you to take training wheels.

Virtual Canvas System allows you to

Change your workflow as needed

No User Stories

Li> Work Without Worry Focus on working according to the needs of the type (work items) or worry about the job title - or post-delivery work or pre-development

To work through the Conan system How long it takes

To take more weight than WIP boundaries, to allow the team

One better and more Construct the continuous improvement process

Provide the transparency and stakeholder participation as any other subtle method

Before making the decision "switch" To Kanban, I encourage you to read a new book from Mike Burrows - "Earburn in the Inside" () and develop more understanding about how Kanban Method can be implemented by your organization and how.

If you have questioned Jira (which I do not think you have done), then I am sorry that I do not have any answer for that part of your question.