With our innovative approach and exceptional team of professionals, we’ve helped many companies maximize results and reach their highest level of success. Read some of our case studies below.
Seamless Transition and Transformation
The Challenge: Hindered by a vendor that refused to address defects/upgrades/etc., this client put their trust in us to do the right thing.
The Approach: After transitioning from the client's previous vendor, the necessary hardware and software upgrades were put into place. Then we tackled the Java application which was riddled with technical debt. A Scrum approach was used which the client supported from the outset. In fact, the client agreed to allow the team to take on a team story every Sprint in order to increase velocity.
The Result: Astonishing. In over 20 sprints there were only 2 occurrences where the anticipated velocity was not exceeded. A pure Kanban approach was undertaken once the project completed and moved to operations. There were many times where the client would say to us "Why doesn't everyone work this way"?
The Challenge: Struggling to find success with Scrum in their O365 SharePoint rollout, this client was extremely frustrated by the lack of progress. They had heard about the various benefits of Agile but weren't able to realize any of them.
The Approach: Once we talked to the team, it was evident that they required training and coaching. We immediately put together a customized course that brought everyone into alignment but also began to build the Agile mindset. Then we assigned a team coach that worked with the team as opposed to dictating dogmatic practices. Together they discovered that Kanban seemed like a better fit than the rigid time-boxed sprints of Scrum.
The Result: Making the switch to Kanban provided immediate results. The team enjoyed the low overhead and was able to visualize the flow.
Collaboration with Distributed Teams
The Challenge: Having never gone through a software development project, this client had some reservations as to how the project would unravel.
The Approach: We wanted to keep things as simple as possible. This led us to Kanban. Furthermore, we decide to use Trello as our Kanban application. The client was extremely impressed with this approach. They could quickly see when they got behind in testing because they had a WIP limit set on the Testing column. Consequently, they were able to accommodate this situation by rotating the testing role amongst a few individuals.
The Result: Feedback was never an issue on this project. Even though the development team and client team were distributed, they managed to collaborate on a daily basis. Instead of going through the monotony of daily standups, the developers would share their screens to review the work that was completed the previous day. The feedback from the client would determine what developers would work on next. The client was so impressed with Kanban that some of them started their own Personal Kanbans.
Small Scale Scrum
The Challenge: Everybody talks about Large Scale Scrum (LeSS), but what about Scrum for small teams. Is it even possible? The general rule is that a Scrum team should consist of 7 to 10 people. Is this a hard rule or merely a suggestion? What can startups do that just don't have the financial resources for 7 people? Are they forced to abandon Scrum? Not necessarily.
The Approach: For this client the team consisted of 2 developers, one of whom also facilitated the role of Scrum Master. The tester was facilitated by the VP of Marketing, and the Product Owner was facilitated by a functional manager.
The Result: These 4 individuals were able to work collaboratively to deliver a project that was ahead of schedule and under budget. What may be even more impressive is that all of the Scrum ceremonies were adhered to. One week sprints were adopted where most days began with the Daily Scrum that lasted no longer than 5 minutes. Sprint Planning was typically completed in under 2 hours as was the Sprint Review. At the outset, Sprint Retrospectives took about half a day but later on that was reduced to under 2 hours as well.