Blue Monitor Software Development
description
Transcript of Blue Monitor Software Development
Material in this demonstration may be subject to NDA and/or the
confidentiality clause in your MSPP Agreement.
Business 2.0
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.
Strategy Creative Technical
―Innovate, Accelerate, and Incubate your ideas in Zero Time‖
High quality & value vs. cost, swiftly and predictably
End-to-end approach, from creative to the data center
Dedicated, passionate team – scalable on the fly
Customers in 15 Countries
Managing 300+ servers
& 1500+ desktops
1,000+ Customers
Over 150+ Apps developed
in 5 years
Blue Monitor Customer
Growth Worldwide
FY06 FY07 FY08
Small Businesses Large EnterprisesMidsized Companies
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
Matrix delivery resources structure
End-2-end iterative development cycle
Well defined engineering process
Flexible change control and configuration management
Turn-key project infrastructure
Project Team 4
Project Team 3
Project Team 2
Project Team 1
Design
Development
QA
OperationsPM
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
Planning GameComplete
FeatureComplete
CodeFreeze
SystemRelease
Iteration 1 Definition Implementation Stabilization Deployment
Planning GameComplete
FeatureComplete
CodeFreeze
SystemRelease
Iteration 2 Definition Implementation Stabilization Deployment
Planning GameComplete
FeatureComplete
CodeFreeze
SystemRelease
Iteration 3 Definition Implementation Stabilization Deployment
Time
Draft req-sready
Final req-sready
Product Management Team
Requirements Definition
Draft UIready
Final UIready
UI Team UI Definition
Draft Artready
Final Artready
Art Team Art Definition
Time
ProductionSupport
ReleaseVerified
Verification
SystemRelease
CodeFreeze
FeatureComplete Test
Feature 1Ready
Implementation Feature 1
Time
Feature 2
Feature NReady
Feature N
Feature 2Ready
Test Feature 1Test
Feature 2Test
ScopeImplemented
FeatureComplete
Feature NTest
Featurecomplete
ReleaseCandidate 1
Stabilization& Deployment
Stabilization
ReleaseCandidate 2
Deployment
In addition to general principles of
Small and frequent iterationsProduct management as ―On-board customers‖
Continuous integration
TQM through Test-driven
development
in the engineering process we also specifically praise:
Scans SVN for
changes
Install is applied to
production servers
• Run tests
• Review code
• Check code in
Build is replicated
to QA serverInstall is prepared
out of tested build
SoftwareEngineers
SubversionCruiseControl
Build Server (URL)
QA Server (URL)
Production Server (URL)
InstallationPackage
Runs tests
Deploys to
Under continuous integration
project stakeholders have instant access to:
• Latest development version of the system
• Latest version in QA
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
Mainline
Version 1.0
Version 1.1
Version N.M
Mainlinecopied
Mainlinecopied
Mainlinecopied
Mainlinecopied
Branchcreated
BrancharchivedQA Branch Production
Branch
Branchcreated
BrancharchivedQA Branch Production
Branch
Version 1.2
Branchcreated
BrancharchivedQA Branch Production
Branch
Time
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