A perfect project : Sprint Zero

A short blurb about the way my current project is being run.
It's the first time I've been on a very agile project and this kicked off two weeks ago.

Sprint Zero had the following elements to it.

  • Team composition was a tech lead, a pair of craftsmen, a product owner.
  • Project kicked off with a Sprint Zero planning meeting that ran a couple hours with everyone available.
  • We mapped out the domain and language used in the domain.
  • Trello was used to create a Sprint Zero board with all members added to it.
  • Members added spike cards and the tech lead ordered them by priority.
  • Github was used to save all the spiked work under one repository.
  • Github also served as the location for our wiki that hosted our play books and domain discovery.
  • A definition of done was written out and stored on the wiki
    • Code is pushed to Github (see GitFlow notes)
    • TDD
    • SOLID and DRY Code Base
    • Code is formatted
    • Static Analysis executed
    • CI Server Build + Test is running Green
    • Branch is merged to Master
    • Deployed to all server environments
    • PO has seen the demo of the working software and approved it in the Test Environment
  • A Construction model was written out with clear definition for swim lanes
  • All libraries and executables within a swim lane had to be independent of each other.
  • The tech lead assessed that there was some completely tested code written by the client that we could re-use for one of our swim lanes feature sets. We decided to reuse that code.
  • We came up with a name for our team and I was amazed at how creative the tech lead was in coming up with a cool logo and an acronym for our Construction Model.
  • Stand up meetings everyday.
  • The fortnight ended with planning for Sprint 1 and sizing.
  • We held a retrospective of our Sprint Zero in preparation for when we might have one again.
  • Every one of these bullet points involved the decision making of all members of the team

Comments

Post a Comment

Popular posts from this blog

Hacking Web App Security

Image
As part of Bob Allen's Code Craftman Saturdays , we had Shanti Suresh present a hands on workshop at Pillar Technology's Forge 4.0 location in Ann Arbor . Her class shed some light onto what cool computer hackers mean when they say they are going to hack into a system. Bob Allen and Shanti Suresh For this workshop,  which ran 5 keyboard hours we started with an introduction to the different terms such as Phase 1 : Introduction to security  Shanti spoke about when and why security became an important aspect of application development and gave a brief overview of the following. Security Authentication Authorization Next we got down and dirty. Phase 2 : Setting up with Zap Using primarily two tools, WebGoat 6.0.1   and Zap  ( beware of using Zap... it makes your computer vulnerable when connected to an external network or internet) we were able to do some sql injection and bypass security. We setup Zap to intercept traffic both to and from the
Read more

Simple MVC3/Razor Fileupload and Storage

Recently I had to add a simple fileupload control in an MVC3 Razor page. It wasn't very difficult to do, thanks to System.Web.Helpers and Microsoft.Web.Helpers. To begin... if you don't have Microsoft.Web.Helpers, find and install through NuGet. pm > Install-Package microsoft-web-helpers Next in your Razor view add the following : @using Microsoft.Web.Helpers @{ ViewBag.Title = "Upload Files"; } @using (Html.BeginForm("Upload","Upload", FormMethod.Post, new { @encType = "multipart/form-data" })) { @FileUpload.GetHtml(initialNumberOfFiles:1, allowMoreFilesToBeAdded:true, includeFormTag:false, addText:"Add Files", uploadText: "Upload File") < input type="submit" name="submit" text="upload" /> } Next in your Upload Controller add the following. The submit button on the Razor page submits the form to the Upload
Read more

Book Summary : How to fail at almost everything and still win big

This is a summary of Scott Adam's book "How to fail at almost everything and still win big". Scott has most likely failed at more things than the average person. This is because he tries his hand at new skills and businesses which in term lead him to big successes such as the Dilbert series.  Major takeaways from the book Let energy be your indicator Decide on what you do based on your energy. If you feel something excites you, let that be the indicator to do more of it. Chances of success are higher on these projects. Goals vs Systems He bluntly says goals are for losers. Goals are specific objectives while systems are to be followed on regular basis. “Losing 10 pounds” is a goal, “eating healthier” is a system. Focus on better systems rather than goals. Systems oriented people feel good every time they follow the system, goals oriented are always busy chasing their goals and once they have attained it feel miserable (and start looking for another one). There are
Read more