Story maps easily represent releases of features that help users accomplish goals. Story maps help show what features should be delivered to create a compelling software experience. Agile projects commonly use task backlogs to manage scope and burn charts to track velocity and predict delivery dates. Simple backlogs and burn charts do not effectively show intermediate accomplishments of value. Expectations outside of the core product team can be more effectively managed by discussing functionality and delivery dates represented in a story map. Coordinating an integrated task backlog (both design centric and code centric tasks) with a story map allows for better scope management and team skills management aimed at hitting intermediate milestones. Disclaimer - This talk outlines thoughts on process and cites actual project examples utilizing several software and paper tools. Shawn is not going to reveal a "silver bullet" software tool.