Part of the Requirements phase should be clearly defining what the goals of the project are, who is impacted and how the changes will improve business operations. Many times, Requirements are statically gathered from the stakeholders without further insight into the real problem. It is imperative that the goals are defined up front and all stakeholders are “bought in” to the project charter at kickoff.
With Confluence, the stakeholders can gain full visibility into initial definitions of the project. After the project is started, it doesn’t end there, they can continue to monitor how the project is shaping up with Requirements, user interactions and mockups constantly updated to reflect current state.