Better explain the project Agility limitations on creation

Problem Definition

The project Agility is a great idea for uncomplicated "create and go" work. However, eventually, the requisites of the project would change and admins would need to modify a workflow, for example. In this situation, admins will find themselves unable to configure the project as needed.

Suggested Solution

Explain the main limitations of the Agility project on the creation process. Examples would be the inability to change the project's workflow or add a second board to the project.

Why this is important

Enhance the user and admin experience. Should avoid the extra hassle of creating a new scrum or kanban project and bulk move all the Agility issues to the new project.

Workaround 

If modifications are needed, a new scrum or kanban project should be created and issues should be bulk moved.