An agile process for data journalism #jpd16
6 likes1,550 views
The document outlines the application of Agile principles in journalism, emphasizing the importance of adapting to changes and defining clear processes for collaboration. It provides a step-by-step guide for journalists to create effective data visualizations, including defining a mission statement, identifying users, brainstorming features, and prioritizing the minimum viable product. The process encourages iterative work with prototyping and measuring results while documenting lessons learned.
An agile process for data journalism #jpd16
- 1. @kaeti http://kaet.io Building data visualizations the agile way
- 2. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan ﬔe Agile Manifesto > > > >
- 3. How does this apply to journalism? + We need to adapt quickly to change + We need clear process so we can work with many different people + We need to improve things and iterate as we go
- 4. 1. Define your mission statement. What is your project’s one sentence manifesto?
- 5. 2. Who are your users? ﬔink about who they are, where they’ll be interacting with a project, and what they need.
- 6. 3. Feature brainstorm. Everything your users might want or need.
- 7. 4. Refine the MVP. What is the minimum viable product? Time to prioritize.
- 8. 5. Sketch, prototype, review. Wash, rinse, repeat. (Work in sprints, set amounts of time with clear deadlines.)
- 9. 6. Ship it. And measure results.
- 10. 7. Document your process and what you’ve learned.
- 11. Find your group!
- 12. What’s the idea? Spend 10 minutos discussing an idea with your group.
- 13. Got an idea? Great! Now it’s time to refine it. What is your manifesto? Tip: ﬔink about what problems you are solving. “How might we…?” 10 minutos
- 14. Each group read their one (or two) sentence project idea 3 minutos
- 15. Time to think about your readers. Who are the users? For each type of user, write down what questions or problems they might have. 15 minutos
- 16. Prioritize those users. Which are the most important users types? ﬔeir needs come first. 5 minutos
- 17. Features brainstorm All the ideas / Todas las ideas 20 minutos
- 18. Sort the features: 1. Must have (necesario) 2. Nice to have 3. “Meh” (no importante) 10 minutos
- 19. How many features are in the must have pile? Get rid of half of them. 5 minutos
- 20. Now you have your list of features, your users, and a defined scope. It’s time to start sketching and prototyping. Remaining time
- 21. Share your ideas and sketches on Twitter with #jpd16agile