Sprint Demo Quotes

We've searched our database for all the quotes and captions related to Sprint Demo. Here they are! All 4 of them:

Blue Bottle wanted to help customers find coffee they’d love. But coffee beans all look alike, so photos wouldn’t be helpful. To find useful solutions, the team did Lightning Demos of websites selling everything from clothes to wine, looking for ways to describe sensory details such as flavor, aroma, and texture. In the end, it was a chocolate-bar wrapper that provided the most useful idea. Tcho is a chocolate manufacturer in Berkeley, California. Printed on the wrapper of every Tcho bar is a simple flavor wheel with just six words: Bright, Fruity, Floral, Earthy, Nutty, and Chocolatey. When Blue Bottle looked at that wheel, they got inspired, and when we sketched, someone repurposed the idea as a simple flavor vocabulary for describing Blue Bottle’s coffee beans: In Friday’s test, and later, at the new online store, customers loved the simple descriptions. It’s a prime example of finding inspiration outside your domain (and yet another reason to be grateful for chocolate).
Jake Knapp (Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days)
There I sat as my dad and the salesperson walked down the aisle. My dad seemed to take some particular interest in the video game that I had just been playing. Maybe interest is too weak of a word, because my dad became engrossed with the demo. I spent the next forty-five minutes crouched behind the boxes across the aisle, waiting for my dad to get bored and to move along. He never moved. Actually, it was pretty impressive how well he did on the game. In that time, he beat three levels and unlocked a few hidden treasures that I never even heard of. I’m starting to wonder if the reason why he’s always telling me to get off the video games is so he can play himself. The salesman urged him a few times to see other set-ups and even try other games, but my dad had none of it. He was like a man possessed on that controller. The whole time, my back was growing sorer from crouching under the shelf and my butt was starting to go numb. Finally, as it came closer to the time he had to leave to pick me up, he graciously thanked the salesman for his time. When they walked away, I burst out from behind the boxes ready to sprint. I needed to beat my dad outside, but the first stride I took sent me collapsing to the ground. Both legs were fully asleep! I shook them like crazy to get the blood flowing back into them. A man walked by with a frightened look on his face, shielding his young son from the sight of me. By the time I got my feet to stop tingling, it was too late. I ran to the front of the store just in time to see my dad get into his car. At that point, I should have cut my losses and admitted to the charade. At least this way, I would have had a ride back. But that’s not how it happened. At that moment, I was sure I could sprint back to the library faster than he could drive there. Three traffic lights stood in between Good Buys and the library. I was counting on a little help from the big Guy upstairs to make those lights red for as long as possible.
Penn Brooks (A Diary of a Private School Kid (A Diary of a Private School Kid, #1))
Agile software teams solve the problems with waterfall by building their software incrementally, making only the decisions around the specific work packages they’ve chosen to complete in a sprint. They delay even the decisions about which work packages or user stories to implement, choosing them out of a backlog at the start of each sprint. They get immediate feedback, first from their own tests and then from the users at a Demo to validate their decisions.
Katherine Radeka (When Agile Gets Physical: How to Use Agile Principles to Accelerate Hardware Development)
Cooler heads prevailed, and we attempted to call off the session. However, this was the salesperson’s first big opportunity, it was a marquee account, and we had a new VP of sales. Over the objections of the technical team, we sprinted down the path of the “dash to demo” and were instructed to perform the demo. This was totally contrary to our well-established sales process and caused severe conflict within the sales team. The SE on the account, being a true professional, decided to make the best of it and spent hours preparing with only limited information.
John Care (Mastering Technical Sales: The Sales Engineer’s Handbook (Technology Management and Professional Development))