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