{"id":12283,"date":"2019-11-19T07:30:05","date_gmt":"2019-11-19T12:30:05","guid":{"rendered":"http:\/\/www.analystik.ca\/blogue\/?p=12283"},"modified":"2021-04-20T11:52:06","modified_gmt":"2021-04-20T15:52:06","slug":"why-proceed-with-your-enterprise-agile-transformation","status":"publish","type":"post","link":"https:\/\/analystik.ca\/blogue\/language\/en\/why-proceed-with-your-enterprise-agile-transformation\/","title":{"rendered":"Why proceed with your Enterprise Agile Transformation?"},"content":{"rendered":"

What is Agile methodology<\/a>?\u00a0 What are its principles?\u00a0 What are the benefits of Enterprise Agile Transformation, turning your company in an Agile Enterprise?<\/p>\n

The result of a search for continuous improvement in the software development process, the Agile methodology appeared at the forefront of ICT in the late 1990s in response to the excesses of major software development projects in terms of schedule, budget and quality of deliverables.<\/span><\/p>\n

And this quest for continuous improvement in software development is in fact based on the search for added value for the company (project scope) and the optimization of the performance of software development teams within fixed schedule and costs as illustrated in the diagram below:\u00a0<\/span><\/p>\n\"Plan\n

<\/p>\n

 <\/p>\n

The spirit of the Agile Manifesto and Enterprise Agility\u00a0<\/span><\/h2>\n

Although there are different Agile approaches including the Agile SCRUM approach, advocates of the Agile methodology will agree and explain that the four values set out in the<\/span> Agile Manifesto<\/span><\/a> encourage a quality-driven software development process by creating products that meet consumers’ needs and expectations.<\/span><\/p>\n

– value individuals and interactions rather than processes and tools<\/b><\/p>\n

– value functional software rather than comprehensive documentation<\/b><\/p>\n

– value customer collaboration rather than contract negotiation<\/b><\/p>\n

– respond to change rather than following a plan<\/b><\/p>\n

 <\/p>\n

And the 12 principles that flow from it, as set out in the <\/span>Agile Manifesto<\/span><\/a>, are designed to create and support continuous integration and a customer-focused work environment that meets the company’s objectives and can respond and turn around quickly as user needs and market forces evolve.<\/span><\/p>\n

The 12 principles set out in the Agile Manifesto:<\/b><\/p>\n

    \n
  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<\/span><\/li>\n
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.<\/span><\/li>\n
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<\/span><\/li>\n
  4. Business people and developers must work together daily throughout the project.<\/span><\/li>\n
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<\/span><\/li>\n
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<\/span><\/li>\n
  7. Working software is the primary measure of progress.<\/span><\/li>\n
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<\/span><\/li>\n
  9. Continuous attention to technical excellence and good design enhances agility.<\/span><\/li>\n
  10. Simplicity–the art of maximizing the amount of work not done–is essential.<\/span><\/li>\n
  11. The best architectures, requirements, and designs emerge from self-organizing teams.<\/span><\/li>\n
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<\/span><\/li>\n<\/ol>\n

    Also, as success attract success, it became natural that other company managers wanted to adapt to their processes the very same principles of Agile Methodology that have contributed so much to the success of software development teams.<\/span><\/p>\n

     <\/p>\n

    Why proceed with your Enterprise Agile Transformation?<\/span><\/h2>\n

    In an ideal world, we would like the continuous improvement process specific to the Agile method to be integrated at all levels of the company, especially in terms of product development, in order to respond more quickly to market changes.<\/span><\/p>\n

    Similarly, we would like the innovation inherent in the Agile method to be strongly encouraged in order to meet customer needs in a more personalized way.<\/span><\/p>\n

    From an entrepreneurial perspective, <\/span>Jean-Loup Richet<\/span><\/a> (Senior Lecturer at the IAE de Paris – Sorbonne Business School) highlights the importance of organizational Agility in innovative and uncertain contexts (start-ups, free electron business units, or even subsidiaries in a state of flux): \u00ab\u00a0The advantage of this approach is that it allows an innovative product to be brought to market faster and more efficiently: customer need orientation, cost and time optimization, no waste, and finally <\/span>better financial performance<\/b> compared to a traditional product development method. \u00bb<\/span><\/p>\n

    Moreover, more than 90% of executives consider \u00ab\u00a0Agility and collaboration\u00a0\u00bb to be essential to the success of their business. This in turn reflects McKinsey & Company’s conclusions that companies and units implementing the Agile methodology have <\/span>better financial profitability<\/b> than those that do not.<\/span><\/p>\n

     <\/p>\n

    The benefits of transforming into an Agile Enterprise<\/span><\/h2>\n

     <\/p>\n

    In a <\/span>recent article<\/span><\/a> and following numerous studies and analyses with companies in the process of Agile transformation, Deloitte summarized the benefits of the Agile Enterprise as follows:<\/span><\/p>\n

    Attributes of the Agile Enterprise<\/b><\/p>\n

    – a homogeneous corporate culture within the entire organization<\/span><\/p>\n

    – end-to-end responsibility of stakeholders in product development<\/span><\/p>\n

    – multifunctional and cross-functional work teams<\/span><\/p>\n

    – adoption of Agile principles by all business units and functions\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Advantages of the Agile Enterprise<\/b><\/p>\n

    – superior increase in customer and employee satisfaction<\/span><\/p>\n

    – organizational flexibility to respond quickly to any changes<\/span><\/p>\n

    – very fast time to market<\/span><\/p>\n

    \u00a0<\/span><\/p>\n

    Conclusion<\/span><\/h2>\n

    In the end, considering all its advantages and benefits, integrating the principles of the Agile methodology involves very little risk for your company other than for those managers who are unable to trust and delegate and, adapt to change.<\/span><\/p>\n

    The latter will most likely also feel in direct competition with some newcomer equivalents specific to the Agile methodology such as SCRUM Masters and Product Owners…<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

    What is Agile methodology?\u00a0 What are its principles?\u00a0 What are the benefits of Enterprise Agile Transformation, turning your company in an Agile Enterprise? The result of a search for continuous improvement in the software development process, the Agile methodology appeared at the forefront of ICT in the late 1990s in response to the excesses of… Read more »<\/a><\/p>\n","protected":false},"author":10,"featured_media":12505,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"What is Agile methodology?\u00a0 What are its principles?\u00a0 What are the benefits of Enterprise Agile Transformation, turning your company in an Agile Enterprise?\u00a0","_seopress_robots_index":"","content-type":"","footnotes":""},"categories":[3421,3567],"tags":[5289,3264,5291,5287],"better_featured_image":{"id":12505,"alt_text":"","caption":"","description":"","media_type":"image","media_details":{"width":1920,"height":1271,"file":"2019\/11\/agile2.jpg","sizes":{"medium":{"file":"agile2-300x199.jpg","width":300,"height":199,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-300x199.jpg"},"large":{"file":"agile2-1024x678.jpg","width":1024,"height":678,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-1024x678.jpg"},"thumbnail":{"file":"agile2-63x63.jpg","width":63,"height":63,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-63x63.jpg"},"medium_large":{"file":"agile2-768x508.jpg","width":768,"height":508,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-768x508.jpg"},"1536x1536":{"file":"agile2-1536x1017.jpg","width":1536,"height":1017,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-1536x1017.jpg"},"bones-thumb-1536":{"file":"agile2-1536x1016.jpg","width":1536,"height":1016,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-1536x1016.jpg"},"bones-thumb-960":{"file":"agile2-960x635.jpg","width":960,"height":635,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-960x635.jpg"},"bones-thumb-600":{"file":"agile2-600x397.jpg","width":600,"height":397,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-600x397.jpg"},"bones-thumb-300":{"file":"agile2-300x199.jpg","width":300,"height":199,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-300x199.jpg"},"post-thumbnail":{"file":"agile2-125x125.jpg","width":125,"height":125,"mime-type":"image\/jpeg","source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2-125x125.jpg"}},"image_meta":{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0","keywords":[]}},"post":12281,"source_url":"https:\/\/analystik.ca\/blogue\/wp-content\/uploads\/2019\/11\/agile2.jpg"},"_links":{"self":[{"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/posts\/12283"}],"collection":[{"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/comments?post=12283"}],"version-history":[{"count":1,"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/posts\/12283\/revisions"}],"predecessor-version":[{"id":12284,"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/posts\/12283\/revisions\/12284"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/media\/12505"}],"wp:attachment":[{"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/media?parent=12283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/categories?post=12283"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/analystik.ca\/blogue\/wp-json\/wp\/v2\/tags?post=12283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}