You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When the Team Playbook came out, I was super excited to share it with my project team because of the potential it has in leveraging techniques that will help get us aligned in a fun and engaging way. We started our exploration of playbooks with the IT Project Poster because we were used to the typical charter that initiated our work which is great at the start of a project.
Ah... the ole project charter. We all know what happens when time elapses from when that keystone document was approved...it typically falls out of focus and, before you know it, the scope creep begins. Then, one day, when everyone is completely lost, someone builds up enough courage to ask the team "what are we trying to do again?". After knocking the digital dust off of this traditional document, which was so coveted, we'd come to find out we were completely off track and actually missing someone who was initially on the team!!
All humor aside, we chose this play because it gave us a chance to get our collective purpose, approach, and high-level thinking in a living page that became the heartbeat of our project space. Plus everyone could refer to the latest information without wasting time sifting through email attachments only to find an older version.
With the IT Project Poster, our entire team was more comfortable in welcoming changes to our project because, as the direction changed, we were able to refer back to the poster and adjust it accordingly. As an added bonus, any changes to the poster were automatically shared with stakeholders who just needed to be informed via notifications - no need to send a separate update.
When the project transitioned from "analysis" to "in flight" the poster also evolved. We attached smart links to reference related materials, knowledge, decisions, etc. and embedded JQL so the Jira epics became our milestones! The "Team" section of the playbook became an excerpt that was then pulled into other Confluence pages so we didn't need to manually update this information in multiple places.
As a result, we always knew what we were doing, why we were doing it, and who was doing it. If you're looking to a fresh approach on aligning your team's goals from the start, give the IT Project Poster a shot - I think you'll be pleased with the outcome!
31 accepted answers