• Home
  • RSS Feed
  • Log in

Multimedia Communication: When to use screencasts/movies in demos.
Posted by Robert van Loghem in the early morning: April 24th, 2009

For the last 9 months I've been working as a team member of Xebialabs on a product called Deployit. The product automates deployments of applications. As any Xebia team we use SCRUM for our development. Now at the end of our two week sprint we give a demo to the product owner and stakeholders of what we've been building.

We demo deploying applications onto a variety of Application Servers and other Middleware, like for instance WebSphere/Oracle-Bea Application Server/Portal, MQSeries, HTTP Servers and so on... Sometimes demo-ing a story, like deploy application A to application server B can take 10 to 15 minutes. That means, for an hour of demo time we can not show every user story that we finished in our sprint. So we only show the important ones. But what happens when demoing a story can take up to 45 minutes? How can can we cram multiple finished stories into the hour?

Multimedia to the rescue! Whenever we have a story that takes a lot of time to demo, we record a screencast when we are preparing, cut out the long waiting parts and then show it as a movie. Please note; we only do this when we demo a user story where we have to wait for a long time. It also is important to tell the product owner and stakeholders that you are playing a movie that normally takes 45 minutes but has been cut down to 2.

Two months ago we worked on WebSphere Portal deployments. The story; Deploy Portlets, Update Skins-Themes-and-Screens and create Virtual Portal was implemented and added to the Fitnesse test suite. To prepare for the demo, I ran the Portal deployment test case. Fitnesse quickly entered all the necessary data into Deployit. (1 second) Then it hit the "Deploy" button and we were off! (sub 1 second). My Macbook Pro's CPU fans started spinning up because the deployment to portal was taking place and after 45 minutes it was done! Before i started the test, i recorded my desktop/screen with my favorite screencast software ScreenFlow. After the test ran, i edited all the parts out of the recording where there was no activity on the screen. That left me with a screencast/recorded movie of about 2 minutes! Perfectly demo-able!

Screenflow recording Deployit
During the demo, we played the movie, we got feedback from the product owner and had lots of time left to demo other user stories. Of course we told the product owner that he shouldn't expect the same portal performance ;) (2 vs. 45 mins.) But that was very clear to him.

It might feel a bit like cheating because we aren't showing the real "live" user story. But sometimes it isn't practical. We want feedback from the product owner and stakeholders. The more feedback we get, the better and using screencasts/movies in demos helps us a great deal.

  • Share/Bookmark

Filed under Agile, Multimedia, Scrum, Xebia Labs | No Comments »



No Responses to “Multimedia Communication: When to use screencasts/movies in demos.”



Leave a Reply

Click here to cancel reply.

Deployment automation for Java application running on Websphere, WebLogic and JBoss

Archives

  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009

Training

  • Workshop Agile Management
    Custom made, in-company
  • Scrum for Team Members
    Custom made, in-company

Xebia Sites

  • Xebia Corporate
  • Xebia France
  • Xebia India

Categories

  • Java (282)
  • Agile (109)
  • General (50)
  • Testing (42)
  • Performance (42)
  • Hibernate (36)
  • Scrum (33)
  • Podcast (31)
  • Architecture (31)
  • Spring (28)
  • SOA (24)
  • Maven (22)
  • Project Management (22)
  • Middleware (23)
    • Deployment (14)
  • Flex (17)
  • JPA (17)
  • Eclipse (15)
  • Xebia Labs (15)
  • Quality Assurance (14)

Tag Cloud

    Semantic Web product owner Introduction to Agile Seam Architecture Maven Ajax qcon fitnesse Spring Grails Testing Agile Awareness Workshop Xebia SOA Poppendieck Hibernate Groovy Scrum Closures Agile IntelliJ JavaOne XML Performance esb Functional Programming Java Scala Lean