630:
821:
921:
When selecting the first few applications to migrate to CD, choose the ones that are easy to migrate but that are important to the business. Being easy to migrate helps to demonstrate the benefits of CD quickly, which can prevent the implementation initiative from being killed. Being important to the
620:
are not obsolete in a CD world, but must be adapted to fit the principles of CD - for example, running multiple long-lived code branches can prove impractical, as a releasable artifact must be built early in the CD process from a single code branch if it is to pass through all phases of the pipeline.
930:
Give a team a visual CD pipeline skeleton that has the full CD pipeline view but with empty stages for those they cannot implement yet. This helps to build up a CD mindset and maintain the momentum for CD adoption. The pipeline skeleton is especially useful when the team's migration to CD requires a
939:
Assign a CD expert to join tough projects as a senior member of the development team. Having the expert on the team helps to build the motivation and momentum to move to CD from inside the team. It also helps to maintain momentum when the migration requires a large effort and a long period of time.
712:
and David Farley (2010) popularized the term; however, since its creation the definition has continued to advance and now has a more developed meaning. Companies today are implementing these continuous delivery principles and best practices. The difference in domains, e.g. medical vs. web, is still
664:
Continuous delivery takes automation from source control all the way through production. There are various tools that help accomplish all or part of this process. These tools are part of the deployment pipeline which includes continuous delivery. The types of tools that execute various parts of the
577:
approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for
912:
Organize the implementation of CD in a way that delivers value to the company as early as possible, onboarding more projects gradually, in small increments and eventually rolling out CD across the whole organization. This strategy helps justify the investment required by making concrete benefits
763:
Reliable releases: The risks associated with a release have significantly decreased, and the release process has become more reliable. With continuous delivery, the deployment process and scripts are tested repeatedly before deployment to production. So, most errors in the deployment process and
699:
are often used when architecting for continuous delivery. The use of
Microservices can increase a software system's deployability and modifiability. The observed deployability improvements include: deployment independence, shorter deployment time, simpler deployment procedures, and zero downtime
806:
Eight further adoption challenges were raised and elaborated on by Chen. These challenges are in the areas of organizational structure, processes, tools, infrastructure, legacy systems, architecting for continuous delivery, continuous testing of non-functional requirements, and test execution
756:
Building the right product: Frequent releases let the application development teams obtain user feedback more quickly. This lets them work on only the useful features. If they find that a feature isn't useful, they spend no further effort on it. This helps them build the right
903:
Without a dedicated team, it can be hard to progress because employees are often assigned to work on other value streams. A multi-disciplinary team not only provides the wide range of skills required for CD implementation but also smooths the communication with related teams.
960:
is a software engineering approach that centers around cultural change, specifically the collaboration of the various teams involved in software delivery (developers, operations, quality assurance, management, etc.), as well as automating the processes in software delivery.
1765:
Continuous deployment is the natural outcome of continuous delivery done well. Eventually, the manual approval delivers little or no value and is merely slowly things down. At that point, it is done away with and continuous delivery becomes continuous
700:
deployment. The observed modifiability improvements include: shorter cycle time for small incremental functional changes, easier technology selection changes, incremental quality attribute changes, and easier language and library upgrades.
764:
scripts have already been discovered. With more frequent releases, the number of code changes in each release decreases. This makes finding and fixing any problems that do occur easier, reducing the time in which they have an impact.
982:
even to production rather than requiring a "click of a button" for that last step. Therefore, continuous deployment can be considered a more sophisticated form of automation. Academic literature differentiates between
894:
Identify each stakeholder's pain points that CD can solve, and sell CD as a painkiller to that stakeholder. This strategy helps to achieve buy-in from the wide range of stakeholders that a CD implementation requires.
753:: Continuous delivery lets an organization deliver the business value inherent in new software releases to customers more quickly. This capability helps the company stay a step ahead of the competition.
616:
can eliminate the step of data migrations and schema changes, often manual steps or exceptions to a continuous delivery workflow. Other useful techniques for developing code in isolation such as
1706:
608:
Developers used to a long cycle time may need to change their mindset when working in a CD environment. Any code commit may be released to customers at any point. Patterns such as
1359:
1172:
Shahin, Mojtaba; Ali Babara, Muhammad; Zhu, Liming (2017). "Continuous
Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices".
789:
Domain restrictions: In some domains, such as telecom, medical, avionics, railway and heavy industries, regulations require customer-side or even on-site testing of new versions.
1778:
Shahin, Mojtaba; Babar, Muhammad Ali; Zahedi, Mansooreh; Zhu, Liming (2017). "Beyond
Continuous Delivery: An Empirical Investigation of Continuous Deployment Challenges".
1508:
Leppänen, M.; Mäkinen, S.; Pagels, M.; Eloranta, V. P.; Itkonen, J.; Mäntylä, M. V.; Männistö, T. (2015-03-01). "The
Highways and Country Roads to Continuous Deployment".
795:
Differences in environments: Different environments used in the development, testing and production can result in undetected issues slipping to the production environment.
636:
Continuous delivery is enabled through the deployment pipeline. The purpose of the deployment pipeline has three components: visibility, feedback, and continually deploy.
913:
visible along the way. Visible benefits, in turn, help to achieve the sustained company support and investment required to survive the long and tough journey to CD.
1427:
553:
643:– All aspects of the delivery system including building, deploying, testing, and releasing are visible to every member of the team to promote collaboration.
507:
578:
more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.
978:
is a software engineering approach which uses automated software deployments. In it, software is produced in short cycles but through automated
922:
business helps to secure the required resources, demonstrates clear and unarguable value, and raises the visibility of CD in the organization.
1267:
802:: Not all quality attributes can be verified with automation. These attributes require humans in the loop, slowing down the delivery pipeline.
709:
474:
1396:
1370:
546:
326:
760:
Improved productivity and efficiency: Significant time savings for developers, testers, operations engineers, etc. through automation.
792:
Lack of test automation: Lack of test automation leads to a lack of developer confidence and can prevent using continuous delivery.
693:(ASRs) such as deployability, modifiability, and testability. These ASRs require a high priority and cannot be traded off lightly.
690:
1333:
464:
316:
649:– Team members learn of problems as soon as possible when they occur so that they are able to fix them as quickly as possible.
1864:
1795:
1689:
1302:
1100:
1079:
605:, then tested by a number of different techniques (possibly including manual testing) before it can be marked as releasable.
539:
439:
195:
180:
459:
831:
1026:
497:
1733:
406:
170:
1242:
1051:
273:
1551:
1001:
678:
396:
391:
147:
1835:
1587:
525:
1006:
670:
655:– Through a fully automated process, you can deploy and release any version of the software to any environment.
416:
129:
109:
278:
215:
205:
155:
713:
significant and affects the implementation and usage. Well-known companies that have this approach include
502:
230:
46:
601:. Code is compiled if necessary and then packaged by a build server every time a change is committed to a
321:
293:
444:
288:
175:
165:
104:
1854:
1602:
591:
210:
190:
1628:
1859:
1463:
1308:
351:
220:
200:
479:
361:
240:
114:
1397:"The Continuous Delivery Pipeline – What it is and Why it's so important in Developing Software"
612:
can be very useful for committing code early which is not yet ready for use by end users. Using
1031:
666:
421:
331:
283:
225:
1780:
2017 ACM/IEEE International
Symposium on Empirical Software Engineering and Measurement (ESEM)
1682:
Continuous
Delivery: reliable software releases through build, test, and deployment automation
1404:
1072:
Continuous
Delivery: Reliable Software Releases Through Build, Test and Deployment Automation
970:
838:
775:
245:
61:
51:
874:
Several strategies to overcome continuous delivery adoption challenges have been reported.
1191:
617:
574:
341:
185:
119:
86:
66:
27:
8:
979:
689:
To practice continuous delivery effectively, software applications have to meet a set of
255:
81:
1749:
1195:
1801:
1533:
1248:
1207:
1181:
1151:
1046:
1036:
454:
842:
629:
1791:
1729:
1685:
1525:
1483:
1298:
1238:
1131:
1096:
1075:
1016:
1537:
1252:
1211:
1805:
1783:
1660:
1517:
1454:
1288:
1280:
1230:
1199:
1155:
1143:
1011:
786:
Customer preferences: Some customers do not want frequent updates to their systems.
718:
674:
598:
411:
374:
356:
346:
71:
1467:
1056:
768:
597:: a set of validations through which a piece of software must pass on its way to
298:
250:
134:
56:
1203:
771:: The number of open bugs and production incidents has decreased significantly.
750:
609:
602:
1665:
1648:
1569:
1848:
1529:
696:
41:
1284:
124:
1458:
1451:
The 12th
Working IEEE/IFIP Conference on Software Architecture(WICSA 2015)
1234:
1225:
Humble, J.; Read, C.; North, D. (2006). "The
Deployment Production Line".
1787:
799:
734:
730:
1521:
1360:"Continuous Delivery: Patterns and Anti-Patterns in Software Lifecycle"
1147:
1090:
1490:
The IEEE International
Conference on Software Architecture (ICSA 2018)
1293:
594:
76:
1489:
1279:. New York, NY: Association for Computing Machinery. pp. 1–9.
1277:
1st International Workshop on Rapid Continuous Software Engineering
1186:
722:
449:
401:
386:
381:
1821:
1269:
Continuous Software Engineering and Beyond: Trends and Challenges
1041:
952:
726:
714:
160:
1485:
Microservices: Architecting for Continuous Delivery and DevOps
1507:
1021:
931:
large effort and mindset changes over a long period of time.
810:
613:
235:
1276:
745:
Several benefits of continuous delivery have been reported.
854:
469:
846:
1753:
1707:"The Relationship between DevOps and Continuous Delivery"
1450:
1132:"Continuous Delivery: Huge Benefits, but Challenges Too"
964:
850:
684:
586:
Continuous delivery treats the commonplace notion of a
1642:
1640:
1638:
1334:"Continuous Deployment with MongoDB at Kitchensurfing"
991:
according to deployment method; manual vs. automated.
778:: A higher level of customer satisfaction is achieved.
1649:"Continuous Delivery: Overcoming adoption challenges"
1777:
1635:
1171:
1167:
1165:
1726:Continuous Delivery and DevOps: A Quickstart guide
1846:
1570:"Velocity 2011: Jon Jenkins, "Velocity Culture""
1162:
1224:
900:Dedicated team with multi-disciplinary members
878:Strategies to Overcome CD Adoption Challenges
1629:"2014-year-continuous-integration-revolution"
1477:
1475:
918:Starting with easy but important applications
547:
16:Software engineering approach of short cycles
1679:
1552:"Implementing Continuous Delivery at Yahoo!"
1447:Towards Architecting for Continuous Delivery
1432:Dr. Dobb's the World of Software Development
1069:
1750:"Continuous Deployment: An Essential Guide"
703:
1472:
1428:"Continuous Delivery: The Agile SUccessor"
1265:
909:Continuous delivery of continuous delivery
811:Strategies to overcome adoption challenges
554:
540:
1664:
1292:
1185:
946:
740:
1723:
1438:
1425:
1394:
1092:A Practical Guide to Continuous Delivery
691:architecturally significant requirements
628:
1704:
1125:
1123:
1121:
1119:
832:instructions, advice, or how-to content
782:Obstacles have also been investigated.
1847:
1600:
1426:Binstock, Andrew (16 September 2014).
1357:
624:
508:Electrical and electronics engineering
1705:Hammond, Jeffrey (9 September 2011).
1673:
1626:
1503:
1501:
1499:
1331:
1088:
965:Relationship to Continuous Deployment
1836:"Building Evolutionary Architecture"
1646:
1481:
1444:
1129:
1116:
814:
685:Architecting for continuous delivery
1680:Humble, Jez; Farley, David (2011).
1070:Humble, Jez; Farley, David (2010).
1027:Continuous configuration automation
841:so that it is more encyclopedic or
659:
13:
1603:"The Case for Continuous Delivery"
1496:
1063:
14:
1876:
1815:
1395:Phillips, Andrew (29 July 2014).
1332:Kluge, Lars (12 September 2013).
1052:Software configuration management
434:Standards and bodies of knowledge
1601:Humble, Jez (13 February 2014).
1588:"Rapid Release At Massive Scale"
1266:Fitzgerald, Brian (2014-06-03).
1002:Application lifecycle management
819:
708:The original CD book written by
679:application lifecycle management
1828:
1771:
1742:
1717:
1698:
1653:Journal of Systems and Software
1620:
1594:
1580:
1562:
1544:
526:Outline of software development
1419:
1388:
1351:
1325:
1259:
1218:
1007:Application release automation
671:application release automation
1:
1822:Continuous delivery practices
1110:
581:
1865:Software development process
7:
1204:10.1109/ACCESS.2017.2685629
994:
927:Visual CD pipeline skeleton
10:
1881:
1453:. Montréal, Canada: IEEE.
968:
950:
891:Selling CD as a painkiller
289:Software quality assurance
1684:. Pearson Education Inc.
1666:10.1016/j.jss.2017.02.013
603:source control repository
1089:Wolff, Eberhard (2017).
704:Implementation and usage
274:Configuration management
1724:Swartout, Paul (2012).
1647:Chen, Lianping (2017).
1627:jFrog (December 2014).
1482:Chen, Lianping (2018).
1445:Chen, Lianping (2015).
1285:10.1145/2593812.2593813
1130:Chen, Lianping (2015).
498:Artificial intelligence
1032:Continuous integration
947:Relationship to DevOps
798:Tests needing a human
741:Benefits and obstacles
667:continuous integration
633:
422:Infrastructure as code
268:Supporting disciplines
1459:10.1109/WICSA.2015.23
1434:. San Francisco: UBM.
1358:Duvall, Paul (2012).
1235:10.1109/AGILE.2006.53
1227:Agile 2006 (Agile'06)
989:continuous deployment
976:Continuous deployment
971:Continuous deployment
776:customer satisfaction
632:
279:Deployment management
1788:10.1109/ESEM.2017.18
1782:. pp. 111–120.
1728:. Packt Publishing.
1407:on 28 September 2015
1229:. pp. 113–118.
980:software deployments
575:software engineering
99:Paradigms and models
28:Software development
1196:2017arXiv170307019S
985:continuous delivery
879:
839:rewrite the content
625:Deployment pipeline
588:deployment pipeline
567:Continuous delivery
22:Part of a series on
1711:Forrester Research
1558:. 23 October 2013.
1522:10.1109/MS.2015.50
1466:2018-11-13 at the
1148:10.1109/MS.2015.27
1095:. Addison-Wesley.
1074:. Addison-Wesley.
1047:Release management
1037:Continuous testing
877:
653:Continually deploy
634:
417:Release automation
294:Project management
1797:978-1-5090-4039-1
1691:978-0-321-60191-9
1304:978-1-4503-2856-2
1102:978-0-134-69147-3
1081:978-0-321-60191-9
1017:Change management
944:
943:
872:
871:
665:process include:
564:
563:
455:ISO/IEC standards
1872:
1855:Software release
1840:
1839:
1832:
1810:
1809:
1775:
1769:
1768:
1762:
1761:
1746:
1740:
1739:
1721:
1715:
1714:
1702:
1696:
1695:
1677:
1671:
1670:
1668:
1644:
1633:
1632:
1624:
1618:
1617:
1615:
1613:
1607:thoughtworks.com
1598:
1592:
1591:
1584:
1578:
1577:
1566:
1560:
1559:
1548:
1542:
1541:
1505:
1494:
1493:
1479:
1470:
1462:
1442:
1436:
1435:
1423:
1417:
1416:
1414:
1412:
1403:. Archived from
1392:
1386:
1385:
1383:
1381:
1376:on June 19, 2018
1375:
1369:. Archived from
1364:
1355:
1349:
1348:
1346:
1344:
1329:
1323:
1322:
1320:
1319:
1313:
1307:. Archived from
1296:
1274:
1263:
1257:
1256:
1222:
1216:
1215:
1189:
1169:
1160:
1159:
1127:
1106:
1085:
1012:Build management
880:
876:
867:
864:
858:
823:
822:
815:
675:build automation
660:Tools/tool types
556:
549:
542:
503:Computer science
412:Build automation
19:
18:
1880:
1879:
1875:
1874:
1873:
1871:
1870:
1869:
1860:Software design
1845:
1844:
1843:
1834:
1833:
1829:
1818:
1813:
1798:
1776:
1772:
1759:
1757:
1748:
1747:
1743:
1736:
1722:
1718:
1703:
1699:
1692:
1678:
1674:
1645:
1636:
1625:
1621:
1611:
1609:
1599:
1595:
1586:
1585:
1581:
1576:. 20 June 2011.
1568:
1567:
1563:
1550:
1549:
1545:
1506:
1497:
1480:
1473:
1468:Wayback Machine
1443:
1439:
1424:
1420:
1410:
1408:
1393:
1389:
1379:
1377:
1373:
1362:
1356:
1352:
1342:
1340:
1330:
1326:
1317:
1315:
1311:
1305:
1272:
1264:
1260:
1245:
1223:
1219:
1170:
1163:
1128:
1117:
1113:
1103:
1082:
1066:
1064:Further reading
1061:
1057:Version control
997:
973:
967:
955:
949:
868:
862:
859:
836:
824:
820:
813:
769:product quality
743:
706:
687:
662:
627:
610:feature toggles
584:
560:
531:
530:
521:
513:
512:
493:
485:
484:
435:
427:
426:
377:
367:
366:
312:
304:
303:
299:User experience
269:
261:
260:
151:
140:
139:
100:
92:
91:
37:
36:Core activities
17:
12:
11:
5:
1878:
1868:
1867:
1862:
1857:
1842:
1841:
1826:
1825:
1824:
1817:
1816:External links
1814:
1812:
1811:
1796:
1770:
1741:
1735:978-1849693684
1734:
1716:
1697:
1690:
1672:
1634:
1619:
1593:
1579:
1561:
1543:
1495:
1471:
1437:
1418:
1387:
1350:
1338:slideshare.net
1324:
1303:
1258:
1243:
1217:
1161:
1114:
1112:
1109:
1108:
1107:
1101:
1086:
1080:
1065:
1062:
1060:
1059:
1054:
1049:
1044:
1039:
1034:
1029:
1024:
1019:
1014:
1009:
1004:
998:
996:
993:
969:Main article:
966:
963:
951:Main article:
948:
945:
942:
941:
937:
933:
932:
928:
924:
923:
919:
915:
914:
910:
906:
905:
901:
897:
896:
892:
888:
887:
884:
870:
869:
827:
825:
818:
812:
809:
807:optimization.
804:
803:
796:
793:
790:
787:
780:
779:
772:
765:
761:
758:
754:
751:time to market
742:
739:
705:
702:
686:
683:
661:
658:
657:
656:
650:
644:
626:
623:
618:code branching
583:
580:
562:
561:
559:
558:
551:
544:
536:
533:
532:
529:
528:
522:
519:
518:
515:
514:
511:
510:
505:
500:
494:
491:
490:
487:
486:
483:
482:
477:
472:
467:
462:
457:
452:
447:
445:IEEE standards
442:
436:
433:
432:
429:
428:
425:
424:
419:
414:
409:
404:
399:
394:
389:
384:
378:
373:
372:
369:
368:
365:
364:
359:
354:
349:
344:
339:
334:
329:
324:
319:
313:
310:
309:
306:
305:
302:
301:
296:
291:
286:
281:
276:
270:
267:
266:
263:
262:
259:
258:
253:
248:
243:
238:
233:
228:
223:
218:
213:
208:
203:
198:
193:
188:
183:
178:
173:
168:
163:
158:
152:
150:and frameworks
146:
145:
142:
141:
138:
137:
132:
127:
122:
117:
112:
107:
101:
98:
97:
94:
93:
90:
89:
84:
79:
74:
69:
64:
59:
54:
49:
44:
38:
35:
34:
31:
30:
24:
23:
15:
9:
6:
4:
3:
2:
1877:
1866:
1863:
1861:
1858:
1856:
1853:
1852:
1850:
1837:
1831:
1827:
1823:
1820:
1819:
1807:
1803:
1799:
1793:
1789:
1785:
1781:
1774:
1767:
1755:
1751:
1745:
1737:
1731:
1727:
1720:
1712:
1708:
1701:
1693:
1687:
1683:
1676:
1667:
1662:
1658:
1654:
1650:
1643:
1641:
1639:
1630:
1623:
1608:
1604:
1597:
1590:. 2017-08-31.
1589:
1583:
1575:
1571:
1565:
1557:
1553:
1547:
1539:
1535:
1531:
1527:
1523:
1519:
1515:
1511:
1510:IEEE Software
1504:
1502:
1500:
1491:
1487:
1486:
1478:
1476:
1469:
1465:
1460:
1456:
1452:
1448:
1441:
1433:
1429:
1422:
1406:
1402:
1398:
1391:
1372:
1368:
1361:
1354:
1339:
1335:
1328:
1314:on 2014-10-25
1310:
1306:
1300:
1295:
1290:
1286:
1282:
1278:
1271:
1270:
1262:
1254:
1250:
1246:
1244:0-7695-2562-8
1240:
1236:
1232:
1228:
1221:
1213:
1209:
1205:
1201:
1197:
1193:
1188:
1183:
1180:: 3909–3943.
1179:
1175:
1168:
1166:
1157:
1153:
1149:
1145:
1141:
1137:
1136:IEEE Software
1133:
1126:
1124:
1122:
1120:
1115:
1104:
1098:
1094:
1093:
1087:
1083:
1077:
1073:
1068:
1067:
1058:
1055:
1053:
1050:
1048:
1045:
1043:
1040:
1038:
1035:
1033:
1030:
1028:
1025:
1023:
1020:
1018:
1015:
1013:
1010:
1008:
1005:
1003:
1000:
999:
992:
990:
986:
981:
977:
972:
962:
959:
954:
938:
935:
934:
929:
926:
925:
920:
917:
916:
911:
908:
907:
902:
899:
898:
893:
890:
889:
885:
882:
881:
875:
866:
856:
852:
848:
844:
840:
834:
833:
828:This section
826:
817:
816:
808:
801:
797:
794:
791:
788:
785:
784:
783:
777:
773:
770:
766:
762:
759:
755:
752:
748:
747:
746:
738:
736:
732:
728:
724:
720:
716:
711:
701:
698:
697:Microservices
694:
692:
682:
680:
676:
672:
668:
654:
651:
648:
645:
642:
639:
638:
637:
631:
622:
619:
615:
611:
606:
604:
600:
596:
593:
589:
579:
576:
572:
568:
557:
552:
550:
545:
543:
538:
537:
535:
534:
527:
524:
523:
517:
516:
509:
506:
504:
501:
499:
496:
495:
489:
488:
481:
478:
476:
473:
471:
468:
466:
463:
461:
458:
456:
453:
451:
448:
446:
443:
441:
438:
437:
431:
430:
423:
420:
418:
415:
413:
410:
408:
405:
403:
400:
398:
395:
393:
390:
388:
385:
383:
380:
379:
376:
371:
370:
363:
360:
358:
355:
353:
350:
348:
345:
343:
340:
338:
335:
333:
330:
328:
325:
323:
320:
318:
315:
314:
308:
307:
300:
297:
295:
292:
290:
287:
285:
284:Documentation
282:
280:
277:
275:
272:
271:
265:
264:
257:
254:
252:
249:
247:
244:
242:
239:
237:
234:
232:
229:
227:
224:
222:
219:
217:
214:
212:
209:
207:
204:
202:
199:
197:
194:
192:
189:
187:
184:
182:
179:
177:
174:
172:
169:
167:
164:
162:
159:
157:
154:
153:
149:
148:Methodologies
144:
143:
136:
133:
131:
128:
126:
123:
121:
118:
116:
113:
111:
108:
106:
103:
102:
96:
95:
88:
85:
83:
80:
78:
75:
73:
70:
68:
65:
63:
60:
58:
55:
53:
50:
48:
45:
43:
42:Data modeling
40:
39:
33:
32:
29:
26:
25:
21:
20:
1830:
1779:
1773:
1764:
1758:. Retrieved
1756:. 2019-10-02
1744:
1725:
1719:
1710:
1700:
1681:
1675:
1656:
1652:
1622:
1610:. Retrieved
1606:
1596:
1582:
1573:
1564:
1556:confreaks.tv
1555:
1546:
1516:(2): 64–72.
1513:
1509:
1484:
1446:
1440:
1431:
1421:
1409:. Retrieved
1405:the original
1400:
1390:
1378:. Retrieved
1371:the original
1366:
1353:
1341:. Retrieved
1337:
1327:
1316:. Retrieved
1309:the original
1268:
1261:
1226:
1220:
1177:
1173:
1142:(2): 50–54.
1139:
1135:
1091:
1071:
988:
984:
975:
974:
957:
956:
886:Description
873:
863:January 2022
860:
837:Please help
829:
805:
781:
749:Accelerated
744:
707:
695:
688:
663:
652:
646:
640:
635:
607:
587:
585:
570:
566:
565:
402:UML Modeling
397:GUI designer
336:
62:Construction
52:Requirements
1766:deployment.
1713:. Forester.
1574:youtube.com
1174:IEEE Access
936:Expert drop
847:Wikiversity
735:Wells Fargo
731:Paddy Power
120:Prototyping
115:Incremental
87:Maintenance
67:Engineering
1849:Categories
1760:2022-11-28
1411:October 9,
1401:DevOps.com
1380:October 9,
1318:2014-10-24
1294:10344/3896
1187:1703.07019
1111:References
855:Wikivoyage
710:Jez Humble
641:Visibility
582:Principles
492:Glossaries
82:Deployment
1659:: 72–86.
1530:0740-7459
1343:3 January
851:Wikibooks
830:contains
774:Improved
767:Improved
595:Poka-Yoke
311:Practices
135:Waterfall
110:Cleanroom
77:Debugging
47:Processes
1538:18719684
1464:Archived
1367:Refcardz
1253:16572138
1212:11638909
995:See also
883:Strategy
757:product.
723:Facebook
647:Feedback
520:Outlines
450:ISO 9001
392:Profiler
387:Debugger
382:Compiler
357:Stand-up
1806:3479812
1612:16 July
1492:. IEEE.
1192:Bibcode
1156:1241241
599:release
573:) is a
191:Lean SD
130:V model
72:Testing
1804:
1794:
1732:
1688:
1536:
1528:
1301:
1251:
1241:
1210:
1154:
1099:
1078:
1042:DevOps
958:DevOps
953:DevOps
845:it to
800:oracle
727:Google
719:Amazon
715:Yahoo!
465:SWEBOK
186:Kanban
161:DevOps
125:Spiral
57:Design
1802:S2CID
1534:S2CID
1374:(PDF)
1363:(PDF)
1312:(PDF)
1273:(PDF)
1249:S2CID
1208:S2CID
1182:arXiv
1152:S2CID
1022:CI/CD
853:, or
614:NoSQL
590:as a
460:PMBOK
375:Tools
236:SEMAT
231:Scrum
105:Agile
1792:ISBN
1730:ISBN
1686:ISBN
1614:2014
1526:ISSN
1413:2015
1382:2015
1345:2014
1299:ISBN
1239:ISBN
1097:ISBN
1076:ISBN
987:and
843:move
733:and
592:lean
475:IREB
470:ITIL
440:CMMI
317:ATDD
226:SAFe
196:LeSS
171:DSDM
1784:doi
1754:IBM
1661:doi
1657:128
1518:doi
1455:doi
1289:hdl
1281:doi
1231:doi
1200:doi
1144:doi
480:OMG
407:IDE
362:TDD
352:SBE
342:DDD
327:CCO
322:BDD
246:TSP
241:TDD
221:RUP
216:RAD
211:PSP
206:MSF
201:MDD
181:IID
176:FDD
166:DAD
156:ASD
1851::
1800:.
1790:.
1763:.
1752:.
1709:.
1655:.
1651:.
1637:^
1605:.
1572:.
1554:.
1532:.
1524:.
1514:32
1512:.
1498:^
1488:.
1474:^
1449:.
1430:.
1399:.
1365:.
1336:.
1297:.
1287:.
1275:.
1247:.
1237:.
1206:.
1198:.
1190:.
1176:.
1164:^
1150:.
1140:32
1138:.
1134:.
1118:^
849:,
737:.
729:,
725:,
721:,
717:,
681:.
677:,
673:,
669:,
571:CD
347:PP
337:CD
332:CI
256:XP
251:UP
1838:.
1808:.
1786::
1738:.
1694:.
1669:.
1663::
1631:.
1616:.
1540:.
1520::
1461:.
1457::
1415:.
1384:.
1347:.
1321:.
1291::
1283::
1255:.
1233::
1214:.
1202::
1194::
1184::
1178:5
1158:.
1146::
1105:.
1084:.
865:)
861:(
857:.
835:.
569:(
555:e
548:t
541:v
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.