Product Development
At Critical Manufacturing, we want to be able to respond quickly to changes and challenges, brought in by our customers. To be able to do that we've embraced Agile methodologies
Agile
“By 2012 agile development methods will be utilized in 80% of all software development projects”-- Gartner Predicts 2010: “Agile and Cloud Impact Application Development Directions”
Our highest priority is to exceed our customers expectations through early and continuous delivery of valuable software.
We are Agile. This is true for our organization, and it's also true for our development process. We chose to use Agile practices for project management and software development because:
- We know that only through frequent delivery of working software the customers will be able to fine-tune their requirements in order to maximize the solution for their competitive advantage
- We've experienced that agile processes promote sustainable development, as teams adapt and become continuously more effective
- We've proven that best practices like continuous integration, automated tests and nightly builds increase both the pace and the quality of our deliveries
- We believe that the best requirements, design and architecture emerge from self-organizing teams
Scrum
“When it comes to selecting an Agile methodology, Scrum is the overwhelming favorite – claiming it is simple, practical, and popular”--Forrester Reports: “Agile Development: Mainstream Adoption Has Changed Agility”
We’ve embraced Scrum, an agile process, for project management as it helps us to focus on the features that are most valuable for our customers and deliver these first
The following list highlights some of the characteristics of the Scrum processes in usage at Critical Manufacturing:
- Self Organized Teams
- Requirements are captured and prioritized as items in a global list of “product backlog”
- Uses generative rules to create an agile environment for delivering projects
- Product progresses in a series of one or half month-long “sprints”
- Product is designed, coded, and tested during the sprint
- At the end of each sprint, there's a workable product
Sprint Status Dashboard
(Click image for full-sized picture)
Sprint Development Status Portal
(Click image for full-sized picture)
