Skip to main content

DevOps and Continuous Planning

Continuous Planning will enable your team to provide a constant flow of functionalities by having a continuously updated plan in place, adjusted to the business requirements. Continuous Integration will implement the plan and provide feedback on development speed to ensure a realistic plan is in place.

Continuous Planning is a practice that requires planners, architects, and agile teams to integrate their plans across the enterprise on an ongoing basis. 
It relies on six principles:
  • Value simplicity
  • The manifesto for agile software development
  • Design thinking
  • Iterative and incremental development
  • Lean management
  • Estimation accuracy

At first we shall explore the capabilities in the DevOps, Continuous Planning and Continuous Integration (CODE, BUILD, TEST).
  • Describe Objectives and Key Results
  • Compare Continuous and Static Planning
  • Describe the six principles of Continuous Planning
  • Characterize Continuous Integration
  • Analyze the effects of Continuous Integration on performance




And also there are 6 Principles of the Continuous Improvement Model
  • Improvements are based on small changes, not only on major paradigm shifts or new inventions
  • Employee ideas are valuable
  • Incremental improvements are typically inexpensive to implement
  • Employees take ownership and are involved in improvement
  • Improvement is reflective
  • Improvement is measurable and potentially repeatable
















Comments

Popular posts from this blog

Juno miluje Jiru! CZ

Není nic lepšího, než když spolu dvě složky fungují naprosto synchronně. Test Case Management systém JunoOne od společnosti Denevy je navržen a vyvinut speciálně pro správu testů a řízení testovacích incidentů a jeho zásadní předností je plná kompatibilita se systémem JIRA. Tuto možnost propojení ocenilo již mnoho spokojených zákazníků. Přečtěte si více informací o našem projektu zaměřeného na integraci JunoOne s nástrojem JIRA v naší case study zde 

Test Strategy is not only document

The purpose of Test Strategy document is in high level definition for entire Test management process and all related activities primarily in concept approaching into test preparation and test execution phases of project. Cooperation all testing activities during the project should be based on main Test policy of organization.
Test management processesImplementation of testing processes is distributed into levels between organization, project and dynamic testing processes.

Organization Test Policy is methodology and document which govern and describe rules for continuous improvement for testing activities within company and describes those areas:Testing definitions, Test process descriptions, Testing Evaluations rules, Quality level definitions and Process improvement rules.Test Strategy (this document) is artefact describes rules and global test approach used by project to deliver quality assurance for defined scope of applications, modules or whole systems with respectation of definiti…

Webové služby - rychlý úvod do testování WS aneb jak získat první odpověď v nástroji SoapUI CZ