Akershoek, “IT4IT™ for Managing the Business of IT.” 2016. Akera, “Edmund Berkeley and the Origins of the ACM,” Communications of the ACM, vol. 2015.Īgile Alliance, “Subway Map to Agile Practices.” 2016.Ī. 2001.Īgile Alliance, “Team Definition,” Glossary. Gojko Adzic, 2012.Īgile Alliance, “Agile Manifesto and Principles,” no. Adzic, Impact Mapping: Making a big impact with software products and projects. Grand Central Publishing, 2012.Īccounting Coach, “What is cost accounting?” 2016. Abrashoff, It’s Your Ship: Management Techniques from the Best Damn Ship in the Navy, 10Th Anniv. Old Tappan, NJ: Pearson Education, Inc., 2015.ĭ. Fisher, The Art of Scalability: Scalable Web Architecture, Processes, and Organizations for the Modern Enterprise (2nd Edition). “The Secret to Amazon’s Success ‒ Internal APIs, by Kin Lane,” The API Evangelist. Walnut Creek, California: Artima, Inc, 2011. White River Junction, VT: Chelsea Green Publishing Company, 2008.Īgile Hiring by Sean Landis. Thinking in Systems: A Primer by Donella Meadows. See definitions of Standard versus Guide in The Open Group Standards Process.
Eventually, the textbook may be the basis for a "Guide", supporting this document in the same way that (for example) the IT4IT Management Guide supports the IT4IT Standard. In general, this document is briefer, drier, and written with a normative should/shall/may/must framing (see IETF RFC 2119, ). However, the textbook also includes extensive quotations, sidebars, anecdotes, cases, tangential elements, personal observations, exercises, and so forth that will not be found in this document. The reader of both documents will, therefore, notice deliberate similarities and identical passages. Such harvesting will not be cited, as it is expected to be substantial. That material is separate and distinct from this document, but the agreement allows for the "harvesting" of material from that text. The resulting textbook, Managing Digital: Concepts and Practices, was contributed by the author and published by The Open Group Press to serve as an experiment in collaborative, open source document development, and also to support worldwide distribution on a low/no-cost basis. Architecture, Digital Strategy, and Portfolio Governance, Risk, Security, and Compliance Structuring the Organization: Product and Function Process Control and Continuous Improvement
Coordination, Execution, and the Delivery Models Work Management Capabilities and Approaches Securing Applications and Digital Products Configuration Management and Infrastructure as Code Compatibility with Enterprise Architecture Relationship of this Document to Other Bodies of Knowledge.Background and Intended Value of this Work.Digital Practitioner Body of Knowledge™ Standard.
0 kommentar(er)
