If a picture is worth a thousand words, a prototype is worth ten thousand words.  At STSI we have learned some best practices about producing rapid prototypes that get users focused on delivering their business needs and away from reams of documentation.


Outline/Structure of the Talk

  • Why prototype?
    • Better than documents
    • Better than mockups
    • It's easier than you think
  • The basic framework
    • Low fidelity UI communicates this is a prototype
    • AngularJS handles URL/Controller logic
    • JSON files provide the initial "database"
  • Removing the need for a backend
    • Modeling the business domain
    • Generating realistic data
      • People
      • Words
      • Volume
      • Statuses
  • Iteratively designing the back-end
    • Angular Services simulate the needed backend calls
    • JSON files simulate the API results
  • Using the prototype to elicit requirements
    • Laddering
    • A/B testing
    • Usability
    • Establish UI "vocabulary" with users
    • Getting offline feedback

Learning Outcome

  • Know how and why to use prototypes to gather requirements

Target Audience

Business Analysts, Front-End Developers, Designers, Architects

schedule Submitted 4 years ago

Public Feedback

comment Suggest improvements to the Speaker

  • 45 Mins

    You probably started your Agile journey with Scrum, which helped. But regression testing still takes forever. New feature tests aren't what they could be and are hard to complete within the Sprint.

    If you have active product owners, the POs helped to improve your product, but there is still a disconnect, between the user story and the tests.  And how do you test "as a, I want, so that"?

    Now you hear you need Agile technical practices to keep improving and you find you need to automate. What are you going to do with your testers?  They really, really know your business, but they don't code.

    If you are a manager, a tester or a product owner, come hear Camille as she shares her experience successfully teaching manual testers Automated Test Driven Development and showing product owners how to write great Acceptance Criteria that are easy to automate.

    In this session you will learn:

    • How to get your product owners, testers and developers to understand each other
    • How to make your business scenarios unambiguous and testable
    • How to avoid brittle tests that need frequent rewriting
    • Which tools and languages are better for testers to learn and why
    • Strategies and techniques for testers to learn test automation
    • Where to find inexpensive and free resources to get started
  • Darren Hoevel
    Darren Hoevel
    Agile Coach
    Pliant Solutions
    schedule 4 years ago
    Sold Out!
    45 Mins

    This presentation was initial created for an executive leadership team being pressure into the practices of Agile. The Organization soon found their to be a huge gap in the understanding of organizational agility, of not only agile, but the conceptual models needed to drive speed, innovation, and creativity. This session will provide a view into an integral view to change. In 45 minutes I will not be able to cover all of the details in every model, however I plan to present these models in such a way that they the audience will understand what resources are at their disposal to leverage when needed and expand their perspective.

  • 45 Mins

    DevOps as a buzzword is gaining traction, but what does it really mean? Managers, non-techies, and developers-new-to-devops will get a guided demo of development automation. See all the cool tools in action - continuous integration, automated testing, cloud deployment, etc. More importantly, we'll walk through what they do, and why that adds value to a project. 

    This talk will...

    • Break down the buzzwords and define some key technical practices in plain english.
    • Uncover the pain that leads teams to seek greater automation.
    • Demonstrate a continuous integration pipeline working in practice via live demo.
    • Diminish the knowledge gap between technical practitioners and managers/analysts/coaches.
    • Level-up the vocabulary of non-technical attendees.
    • Introduce practices to developers who don't yet work in an automated environment.
    • Spark "ah-ha" moments to convert skeptics into DevOps believers!

    By the way, all of the tools in the demo are some combination of free and/or open source. DevOps doesn't have to cost a lot.

  • Liked Christy Hermansen

    Christy Hermansen - Inside the GSA – a Case Study of user-centered Agile in a high-profile government agency

    45 Mins
    Case Study

    This unique journey will transport you deep inside the world of the General Services Administration (GSA) Integrated Award Environment (IAE).  You will see how user-centered Agile is transforming the way software applications are engineered, how users' voices have been integrated with large-scale Agile development, and what issues we encountered along the way.

    When Eric Schmidt, former CEO of Google, predicted, "Everything in the future online is going to look like a multiplayer game," perhaps he was envisioning a user community such as ours.  The IAE family of software applications have more than a million users representing federal, state, local, and tribal government organizations; congressional staff; large and small businesses; universities, schools, and hospitals; non-profit organizations; foreign entities; private citizens and others.  Our greatest challenge is the diversity of our user base, resembling a massive multiplayer game in many ways. 

    This case study looks inside a major reengineering effort to migrate 10 legacy applications into an integrated environment while at the same time transitioning from Waterfall to Agile development.  It tells the story of how IAE users have shaped our transformation thus far.  



  • 45 Mins

    The retrospective is one of the most powerful Agile ceremonies. They require you to learn from your experiences and challenge you to continuously improve.

    In this interactive session, you’ll explore retrospectives in depth, including activities to bring out different personality types and patterns for different levels of team maturity.



    Scrum has gifted a few Scrum Ceremonies to the world: Sprint Planning, Daily Standups, Backlog Grooming and the Sprint Retrospective. The Retrospective is one of the most important and the most powerful Ceremony.

    Retrospectives are required to learn from the experience and improve upon. To he ever-growing competition, the Organizations need to learn a lot from their experience and change accordingly (Charles Darwin: Survival of the fittest).

    If it is performed well, it can yield wonderful outcomes to improve anything/everything.

    Over a period of time, the teams start feeling bored about the same Old Retrospective (Glad, Sad or Mad, etc) so a lot of Fun/engagement part needs to be added to the same.

    In the current times, Retrospectives need a rebirth otherwise Retrospectives will die and the Learning curve will die as well!

  • 45 Mins

    There has been a lot of talk lately about Software Craftsmanship. Most of this talk has been centered around how to take existing, skilled programmers and turn them into Craftsmen. What about those who are just entering the field? In this talk, we will explore a new approach to fulfilling the entire journey from Apprentice to Master, both from a personal and organizational level. We will also look at how to get such a program started, and how to bring the existing team along.

  • Liked Dave Rooney

    Dave Rooney - Emergent Design with Test-Driven Development

    90 Mins

    This workshop shows how Test-Driven Development (TDD) is used to enable emergent design. Using a simple but representative example in Java, the presenter will demonstrate how a low-level design naturally emerges when using the TDD cycle of test/code/refactor. The audience will be involved by suggesting the next steps and also by pairing with the presenter.

    Note that the goal of the session isn't necessarily to have a complete working example at the end, but to illustrate the process of low-level design through TDD.