archive-org.com » ORG » A » ANDREWCOX.ORG

Total: 185

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Agile Product Ownership with Jeff Patton - Andrew Cox
    Product Manager business value Development Architect feasibility and innovation User Experience Expert usability and desirability This team of Product Owners has the joint responsibility for Determining what functionality goes into each release Managing and prioritizing the product backlog Reviewing quality and progress at retrospectives User Story Mapping I d read about user story mapping before but I ve never tried it and it didn t resonate with me until Jeff explained it and had us try it out with a real problem User Story Mapping is about visualizing all the steps a user does to gain value from the system It forms a narrative left to right with sub tasks or details filled in below each major action There are two really important benefits of a story map It forces you to think in terms of how a user will use and gain value from an application as opposed to just feature sets It makes you really think about what a Minimal Viable Product MVP is If you get the user story map right you shouldn t need to estimate releases Of course you should still be able to estimate when you ll get done based on your velocity but if you ve truly mapped an MVP you don t need to set a release deadline and then back your way into it with feature sets If you haven t heard of user story mapping or have overlooked it I encourage you to read up on it and give it a shot I can t speak from experience yet but it s one of the practices that I plan to start very soon Collaborative Acceptance Criteria This is the simple idea that a cross functional team determines what the definition of Done is for a story It s not the tester s job to discern acceptance criteria from a requirements document the acceptance criteria needs to be agreed upon by the developer tester and product manager The big wins from my perspective are Testers get the information about how a feature should work directly from the developer and product manager Developers learn the way testers think and what common failure cases they look for Acceptance Criteria can be a substitute for a formal Requirements document Retrospectives My team has regular bi weekly retrospectives but they aren t as structured as Jeff suggests There were some new ideas to me here that I think are really great such as Do a walk through of new functionality and note any UX or functional issues Rate the features code user experience and quality on a scale of 1 5 Review velocity and note reasons for any major variations Identify any new risks or user stories By having the walkthrough as the focus for the retrospective all concerned parties can raise any issues or help steer the direction of the next iteration One of my favorite aspects of this is that the UX representative gets to point out any minor cosmetic issues and get

    Original URL path: http://andrewcox.org/post/3638171896/agile-product-ownership-with-jeff-patton (2016-04-30)
    Open archived version from archive


  • Andrew Cox
    what they should do to get better I always say try to be the worst guy in whatever band you re in Pat Metheny Earlier Posts Page 25 of 86

    Original URL path: http://andrewcox.org/page/25 (2016-04-30)
    Open archived version from archive

  • Whenever young guys ask me what they should do to... - Andrew Cox
    ask me what they should do to get better I always say try to be the worst guy in whatever band you re in Pat Metheny Previous Post Next Post

    Original URL path: http://andrewcox.org/post/3492821871/whenever-young-guys-ask-me-what-they-should-do-to (2016-04-30)
    Open archived version from archive

  • Andrew Cox
    fallacy to suggest that start ups have to trade away quality in exchange for getting to market faster with their first release Start Ups Must One Day Become Stay Ups Software People Inspiring Earlier Posts Page 26 of 86 Later

    Original URL path: http://andrewcox.org/page/26 (2016-04-30)
    Open archived version from archive

  • The Kanban Method is not a software development or... - Andrew Cox
    2010 The Kanban Method is not a software development or project management methodology David J Anderson and Associates Back to Basics with Kanban Previous Post Next Post Follow me on

    Original URL path: http://andrewcox.org/post/1381502416/the-kanban-method-is-not-a-software-development-or#_=_ (2016-04-30)
    Open archived version from archive

  • Sarasvathy explains that entrepreneurs’ aversion... - Andrew Cox
    entrepreneurs aversion to market research is symptomatic of a larger lesson they have learned They do not believe in prediction of any kind How Great Entrepreneurs Think Previous Post Next

    Original URL path: http://andrewcox.org/post/3343839879/sarasvathy-explains-that-entrepreneurs-aversion#_=_ (2016-04-30)
    Open archived version from archive

  • It’s a demonstrable fallacy to suggest that... - Andrew Cox
    a demonstrable fallacy to suggest that start ups have to trade away quality in exchange for getting to market faster with their first release Start Ups Must One Day Become Stay Ups Software People Inspiring Previous Post Next Post Follow

    Original URL path: http://andrewcox.org/post/3410867135/its-a-demonstrable-fallacy-to-suggest-that (2016-04-30)
    Open archived version from archive

  • Andrew Cox
    Sarasvathy explains that entrepreneurs aversion to market research is symptomatic of a larger lesson they have learned They do not believe in prediction of any kind How Great Entrepreneurs Think Earlier Posts Page 27 of 86 Later Posts Follow me

    Original URL path: http://andrewcox.org/page/27 (2016-04-30)
    Open archived version from archive



  •