Blue Monitor Systems Software Development Services
- 1. Business 2.0 Material in this demonstration may be subject to NDA and/or the confidentiality clause in your MSPP Agreement.
- 2. Blue Monitor Systems has a corporate strategy that encourages employee-owners to think and act like responsible owners helping the company perform at a higher level. The company's founders and employees are dedicated to the creation and delivery of quality creative, technical, and scientific services which contribute to the security and well being of communities worldwide. We believe that if we do good socially for the communities where we operate, our business will reap the benefits financially. Blue Monitor is an employee-owned company of people dedicated to delivering best-value services and solutions based on creativity, and innovative applications of science and technology.
- 3. ―Innovate, Accelerate, and Incubate your ideas in Zero Time‖ Strategy Creative Technical
- 4. End-to-end approach, from creative to the data center High quality & value vs. cost, swiftly and predictably Dedicated, passionate team – scalable on the fly
- 5. Blue Monitor Customer Customers in 15 Countries Growth Worldwide Managing 300+ servers & 1500+ desktops 1,000+ Customers Over 150+ Apps developed in 5 years FY06 FY07 FY08
- 6. Small Businesses Midsized Companies Large Enterprises
- 7. The ―Zero Time‖ Method: Enhanced mix of Agile (XP, Scrum) and traditional (PMBOK, CMMI, RUP) approaches Based on Blue Monitors team experience of successful delivery of 400+ man/years programs with monthly major releases Based on real appreciation of Agile ideas but understanding that pure Agile does not work well for medium and large projects and programs
- 8. Matrix delivery resources structure End-2-end iterative development cycle Well defined engineering process Flexible change control and configuration management Turn-key project infrastructure
- 9. Project Team 1 Project Team 2 Project Team 3 Project Team 4 Design QA PM Development Operations Each project team Is combined of specialists from 4 separate departments: Design, Engineering, Test, Operations Each account Is managed by an experienced Project Manager and supervised by one of the Company Executives
- 10. Time Iteration 1 Definition Implementation Stabilization Deployment Planning Game Feature Code System Complete Complete Freeze Release Iteration 2 Definition Implementation Stabilization Deployment Planning Game Feature Code System Complete Complete Freeze Release Iteration 3 Definition Implementation Stabilization Deployment Planning Game Feature Code System Complete Complete Freeze Release
- 11. Time Product Requirements Management Team Definition Draft req-s Final req-s ready ready UI Team UI Definition Draft UI Final UI ready ready Art Team Art Definition Draft Art Final Art ready ready
- 12. Time Implementation Feature 1 Feature 2 Feature N Feature 1 Feature 2 Feature N Ready Ready Ready Test Feature 1 Feature 2 Feature N Feature Test Test Test Complete Test Scope Feature Implemented Complete Stabilization Stabilization Deployment Verification Production & Deployment Support Feature Release Release Code System Release complete Candidate 1 Candidate 2 Freeze Release Verified
- 13. In addition to general principles of Small and frequent iterations Product management as ―On-board customers‖ in the engineering process we also specifically praise: Continuous integration TQM through Test-driven development
- 14. • Run tests • Review code Scans SVN for Software • Check code in Cruise Subversion changes Engineers Control Runs tests Deploys to Install is prepared Build is replicated out of tested build QA Server to QA server Build Installation (URL) Server Package (URL) Install is applied to production servers Production Under continuous integration Server project stakeholders have instant access to: (URL) • Latest development version of the system • Latest version in QA
- 15. Time Mainline Mainline Mainline Mainline copied copied copied copied Mainline Version 1.0 Branch Branch created QA Branch Production archived Branch Version 1.1 Branch Branch created QA Branch Production archived Branch Version 1.2 Branch Branch created QA Branch Production archived Version N.M Branch At any moment of time there are next branches: 1. Mainline — holds implementation codebase 2. QA branch — holds stabilization codebase 3. Production branch — holds production codebase 4. Archive branches — holds old versions codebases
- 16. Confluence is an enterprise wiki-style knowledge management system that makes it easy for your team to collaborate and share knowledge JIRA is a bug tracking, issue tracking, and project management system that has been designed with a focus on task achievement, is instantly usable and is flexible to work with. Subversion is an open source version control system used to maintain current and historical versions of files such as source code, web pages, and documentation Cruise Control is a framework for a continuous build process, that includes plug-ins for email notification, Ant, and various source control tools. It is integrated with Subversion and Code Collaborator – automated code reviews system. Adobe Acrobat Connect (former Macromedia Breeze) is a web conferencing software with well developed collaboration and information sharing features Adobe Acrobat Connect