If I were in charge, Id #failOr, how software development best practices can work for                    newsrooms, too.  ...
#FAILWhy fail?
Coding culture: Not just hoodies and headphones  Software development best practices can  help a newsroom:   ● Fail fast  ...
Fail fast: Plan and iteratePlan for iteration: ● Break the project into segments ● Roll out the project in stages ● Build ...
Fail fast: Plan and iterate We do this already.
Fail often: Agile execution● Stay on task: Daily standup meeting● Document, document, document:  Tools to help track progr...
Fail often: Agile execution
Fail smart: Evaluate and collaborate ● Quality assurance: Engage your reader   community. ● Staff to staff "code review": ...
Fail smart: Evaluate and collaborate    Support each other as a    team (and as a community)
And then, you dance!                                   Thank YouSpecial thanks to @lisawilliams, @d6, Mayfirst/PeopleLink,...
Upcoming SlideShare
Loading in …5
×

ONA11: Erika Owens, "If I Were in Charge, I'd _____" Presentation

479 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
479
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ONA11: Erika Owens, "If I Were in Charge, I'd _____" Presentation

  1. 1. If I were in charge, Id #failOr, how software development best practices can work for newsrooms, too. Erika Owens @erika_owens
  2. 2. #FAILWhy fail?
  3. 3. Coding culture: Not just hoodies and headphones Software development best practices can help a newsroom: ● Fail fast ● Fail often ● Fail smart
  4. 4. Fail fast: Plan and iteratePlan for iteration: ● Break the project into segments ● Roll out the project in stages ● Build detailed requirements and flowcharts for newsroom workflows and processes
  5. 5. Fail fast: Plan and iterate We do this already.
  6. 6. Fail often: Agile execution● Stay on task: Daily standup meeting● Document, document, document: Tools to help track progress, issues● Keep on task: Display and communicate about your plans, workflows
  7. 7. Fail often: Agile execution
  8. 8. Fail smart: Evaluate and collaborate ● Quality assurance: Engage your reader community. ● Staff to staff "code review": present feedback and suggestions. ● Followthrough: Be transparent about updates and accountable to one another
  9. 9. Fail smart: Evaluate and collaborate Support each other as a team (and as a community)
  10. 10. And then, you dance! Thank YouSpecial thanks to @lisawilliams, @d6, Mayfirst/PeopleLink, and The Notebook.Please contact me with any questions or if you want to talk tech (specifically drupal, civiCRM,women who tech) and journalism.Erika Owens@erika_owens

×