Agile Practices

From DevSummit
Revision as of 23:59, 24 November 2015 by Jucsanch (talk | contribs) (Created page with "Grant tells of Exygy of trying to do agile for their client services *Hit some bumps. Focused too much on the practices instead of the principles. *Tries pair programming, imp...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Grant tells of Exygy of trying to do agile for their client services

  • Hit some bumps. Focused too much on the practices instead of the principles.
  • Tries pair programming, improved code quality but not value delivery
  • Instead of code quality, talk about code scalability
  • Developing a set of best practices to support agile principles
  • Genevieve is working with nonprofits to focus on outcomes
  • Creating an iterative process has been most impactful on project management
  • When doing services, salespeople should sell the process not solutions
  • Using pivotal tracker forces some process on you
  • The concept of a backlog and working on the most important thing has been powerful
  • What to do if the clients priorities don't make sense?
    • Clients jump to the very end sometimes.
    • Agile says that you should have a product owner
    • Exygy pairs one client representative with one staff guide
    • Mike thinks ownership is more about owning the process to build consensus
    • It really depends on the client
    • Tread lightly with people's emotions about their projects
  • Agile is a toolbox, pull practices out as needed
  • Have the designer talk to developers earlier in the process
  • Screen early and often to identify problems when they are manageable
  • Leading an org is like playing an organ, you need to move all the levers
  • Micro and macro viewing is important
  • Keep breaking things down as much as possible
  • Mike likes using Epics in JIRA to break things down by area
  • Kanban is a practice/philosophy. The source of active/backlog/icebox columns
  • Your work in progress only has three things in it at a time
  • Trello is a very simple implementation
  • Lean Kit is a simple Kanban board
  • Retrospectives are important. Review after every iteration.
  • Ask yourself "is this working?"
  • Ask the team for:
    • likes of what is working well
    • wishes for improvements
    • wonders / questions
  • Wiping the slate clean is a huge benefit of iterations
  • Product road maps are the worst. Projects are not a highway.
  • Product terrain maps are better, list obstacles and destination but keep exploring
  • Get a big win early to get people on board with an iterative process

Resources=

No perfect tool, and even if there was it will not be when your process changes

  • Reading: The Toyota Way says problems are useful
  • Tool: Stories On Board helps break things down
  • Reading: Personal Kanban to bring it into your own life
  • Tool: Workflowy lets you drill down
{"cc_re__cc_re__cc_by_sa_3_0": ["0\" title=\"Permanent link to this revision of the page\">Permanent link</a></li><li id=\"t-info\"><a href=\"/index.php?title=Agile_Practices&amp;action=info\" title=\"More information about this page\">Page information</a></li></ul>\n\t\t\n\t</div>\n</nav>\n\n\n\t\n</div>\n\n</div>\n\n<footer id=\"footer\" class=\"mw-footer\" role=\"contentinfo\" >\n\t<ul id=\"footer-info\" >\n\t\t<li id=\"footer-info-lastmod\"> This page was last edited on 22 November 2016, at 20:20.</li>\n\t\t<li id=\"footer-info-copyright\">Content is available under <a class=\"external\" rel=\"nofollow\" href=\"http://creativecommons.org/licenses/by-sa/3.0/\">Creative Commons Attribution Share Alike</a> unless otherwise noted.</li>\n\t</ul>\n\t<ul id=\"footer-places\" >\n\t\t<li id=\"footer-places-privacy\"><a href=\"/index.php?title=DevSummit:Privacy_policy\" title=\"DevSummit:Privacy policy\">Privacy policy</a></li>\n\t\t<li id=\"footer-places-about\"><a href=\"/index.php?title=DevSummit:About\" title=\"DevSummit:About\">About DevSummit</a></li>\n\t\t<li id=\"footer-places-disclaimer\"><a href=\"/index.php?title=DevSummit:General_disclaimer\" title=\"DevSummit:General disclaimer\"", "ces\" >\n\t\t<li id=\"footer-places-privacy\"><a href=\"/index.php?title=DevSummit:Privacy_policy\" title=\"DevSummit:Privacy policy\">Privacy policy</a></li>\n\t\t<li id=\"footer-places-about\"><a href=\"/index.php?title=DevSummit:About\" title=\"DevSummit:About\">About DevSummit</a></li>\n\t\t<li id=\"footer-places-disclaimer\"><a href=\"/index.php?title=DevSummit:General_disclaimer\" title=\"DevSummit:General disclaimer\">Disclaimers</a></li>\n\t</ul>\n\t<ul id=\"footer-icons\" class=\"noprint\">\n\t\t<li id=\"footer-copyrightico\"><a href=\"http://creativecommons.org/licenses/by-sa/3.0/\"><img src=\"/resources/assets/licenses/cc-by-sa.png\" alt=\"Creative Commons Attribution Share Alike\" width=\"88\" height=\"31\" loading=\"lazy\"/></a></li>\n\t\t<li id=\"footer-poweredbyico\"><a href=\"https://www.mediawiki.org/\"><img src=\"/resources/assets/poweredby_mediawiki_88x31.png\" alt=\"Powered by MediaWiki\" srcset=\"/resources/assets/poweredby_mediawiki_132x47.png 1.5x, /resources/assets/poweredby_mediawiki_176x62.png 2x\" width=\"88\" height=\"31\" loading=\"lazy\"/></a></li>\n\t</ul>\n\t<div style=\"clear: both;\">"], "copyright__copyright__copyright": ["are the worst. Projects are not a highway.\n  \u2022 Product terrain maps are better, list obstacles and destination but keep exploring\n  \u2022 Get a big win early to get people on board with an iterative process\n\nResources=\n\nNo perfect tool, and even if there was it will not be when your process changes\n\n  \u2022 Reading: The Toyota Way says problems are useful\n  \u2022 Tool: Stories On Board helps break things down\n  \u2022 Reading: Personal Kanban to bring it into your own life\n  \u2022 Tool: Workflowy lets you drill down", "are the worst. Projects are not a highway.\n  \u2022 Product terrain maps are better, list obstacles and destination but keep exploring\n  \u2022 Get a big win early to get people on board with an iterative process\n\nResources=\n\nNo perfect tool, and even if there was it will not be when your process changes\n\n  \u2022 Reading: The Toyota Way says problems are useful\n  \u2022 Tool: Stories On Board helps break things down\n  \u2022 Reading: Personal Kanban to bring it into your own life\n  \u2022 Tool: Workflowy lets you drill down"]}