Kevin Thompson

The Thermo Fisher Scientific engagement was my first opportunity to apply the ideas from my Agile Hardware research in a

One of the predictions from my Agile Hardware research was that swarming would be much less effective in hardware development

One of the predictions from my Agile Hardware research was that Sprint Planning would need to account for the specialized

One of the predictions from my Agile Hardware research was that Velocity would behave differently when teams estimated work in

Every Scrum team must estimate work in order to plan Releases and Sprints. At Thermo Fisher Scientific, we used the

One of the predictions from my Agile Hardware research was that the traditional software Quality Assurance model would not transfer

One of the predictions from my earlier research into Agile hardware development was that Product Owners would write a much

One of the surprises during the Thermo Fisher Scientific engagement was that the team initially struggled with writing Epics and

One of the more surprising discoveries during the Thermo Fisher Scientific engagement involved the role of User Stories. In software

As the Thermo Fisher Scientific project progressed, I began to notice another fundamental difference between hardware and software development. Even

One of the first challenges facing the Thermo Fisher Scientific team was defining the scope of the product in a