Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Mikey Ariel - My personal tech-writing agile manifesto

Agile development - you either love it or you hate it. But can you change your mind about it? What *does* make agile methodologies work, and how can I make them work for me? How can I build my own personal, portable Agile Manifesto, that I can apply to any working environment at any company? And what does all of this have to do with technical writing anyway?

  • Be the first to comment

Mikey Ariel - My personal tech-writing agile manifesto

  1. 1. 1 MY PERSONAL TECH-WRITING AGILE MANIFESTO Mikey Ariel Senior Technical Writer, Red Hat Devel.cz, June 2014
  2. 2. 2 Why Are We Here? ● What can the Agile Manifesto do for my docs ● The Scrum-Kanban dynamic duo ● Where did agile development get its bad reputation
  3. 3. 3 Who Am I? ● Technical writer ● Former Scrum master (SAFe / ScrumBan) ● Documentarian
  4. 4. 4 Who am I Not? ● Engineer ● Expert on agile development ● Veteran of open source
  5. 5. 5
  6. 6. 6 Ask What the Agile Manifesto Can Do for You Individuals and interactions over Processes and tools read: Get to know your stakeholders
  7. 7. 7 Ask What the Agile Manifesto Can Do for You Working software over Comprehensive documentation read: Document and learn by example
  8. 8. 8 Ask What the Agile Manifesto Can Do for You Customer collaboration over Contract negotiation read: Find your customers
  9. 9. 9 Ask What the Agile Manifesto Can Do for You Responding to change over Following a plan read: Keep up with the development cycle
  10. 10. 10 The Scrum Playbook ● Sprints: Time-boxing abstract timelines ● Backlog: How good is “good enough” ● Planning and retrospective: Staying accountable ● DoD: Crossing all the t's ● Scrum master: Herding all the cats
  11. 11. 11 Kanban Board Games ● Cards represent tasks ● Columns represent development stages ● Blockers sound the alarms early ● Board is accessible and transparent to all ● Analysis and integration with tracking tools
  12. 12. 12
  13. 13. 13 Where is the Fail? ● Power to the people... who don't want it ● Method tailoring or fear of change? ● Scrum of scrums of scrums of scrums ● Yo dawg, we heard you like meetings... ● Same %&$#, different names
  14. 14. 14
  15. 15. 15 QUESTIONS? COMMENTS? mariel@redhat.com @thatdocslady Voting and feedback welcome! http://www.feedbando.com/mobile/techwrite Oh yeah, we're hiring! jobs.redhat.com

    Be the first to comment

    Login to see the comments

  • cmmtech

    Jul. 30, 2014

Agile development - you either love it or you hate it. But can you change your mind about it? What *does* make agile methodologies work, and how can I make them work for me? How can I build my own personal, portable Agile Manifesto, that I can apply to any working environment at any company? And what does all of this have to do with technical writing anyway?

Views

Total views

3,968

On Slideshare

0

From embeds

0

Number of embeds

2,834

Actions

Downloads

6

Shares

0

Comments

0

Likes

1

×