![]() Next step: Keep track of your requirements If you use Requirement Yogi, list requirements rather than the Confluence page, this is especially useful for bug reports. Raise JIRA development tickets and link them to Confluence pages. See the list of linked issues at the top of the pageįrom Requirement Gathering to JIRA Issuesįor the requirement gathering phase, the best practice is to initialize a space with subpages for customer interviews, contract negotiation and retroengineering artifacts, such as screenshots and cartography.This is the knowledge base of your project: It is a picture of the current state of the documentation.Ītlassian already has integrations between the two products: One should however notice that an issue doesn’t give an overview of a project, unless you live in a flat world with only one dimension.ĭocuments resulting of activities such as early analysis, requirement gathering, design and customer interviews should be kept in Confluence. The reason why we’d advise to keep all “change management” in JIRA is because you want to track all sprints, features, bug reports and requests of any kind with an “issue number.” They help track the origin, stakeholders, estimates and discussions about every change. While JIRA is ideal for tasks, Confluence is better at capturing text and content. ![]() Today we’re going to look at managing business and functional requirements and technical specifications in Confluence. Its ergonomics and perks, such as macros, document organization and teamwork features, bring up new ways of organizing your teams, but this has already been discussed in a previous article (“ The myth of the shared network drive” in French). Atlassian Confluence is a mind-blowing tool for capturing information on a project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |