{"id":264,"date":"2016-02-05T19:28:42","date_gmt":"2016-02-05T19:28:42","guid":{"rendered":"http:\/\/agile-egg.com\/wpagile\/?page_id=264"},"modified":"2016-02-29T20:01:06","modified_gmt":"2016-02-29T20:01:06","slug":"organisation","status":"publish","type":"page","link":"https:\/\/agile-egg.com\/wpagile\/front-page\/organisation\/","title":{"rendered":"Organisation, Flex Resourcing &amp; Partnerships"},"content":{"rendered":"<p>The story about the organisation is actually quite short due to their relatively simple design \u2013 it is all about teams<\/p>\n<p>The ETS organisation shape iterated from the early start like this\u2026<\/p>\n<p><a href=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Early-team-structure.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-width: 0px;\" title=\"Early team structure\" src=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Early-team-structure_thumb.jpg\" alt=\"Early team structure\" width=\"754\" height=\"442\" border=\"0\" \/><\/a><\/p>\n<p>\u2026to this<\/p>\n<p><a href=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Team-structure-second-page.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-width: 0px;\" title=\"Team structure second page\" src=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Team-structure-second-page_thumb.jpg\" alt=\"Team structure second page\" width=\"754\" height=\"409\" border=\"0\" \/><\/a><\/p>\n<p>In all not that much difference between the two, with core components being:<\/p>\n<ul>\n<li><strong><em>Solutions Leadership Forum<\/em><\/strong> \u2013 essentially an advisory board including co-opted representatives from teams outside development, including Security, Architecture, Technology Operations and Business Change<\/li>\n<li><strong><em>Solutions Delivery Leadership<\/em><\/strong> \u2013 the ETS management team<\/li>\n<li><em><strong>Solutions Governance<\/strong><\/em> \u2013 Guardians and coaches on key capabilities and standards such as Customer Experience, Integration, Development Method, Development\u00a0Standards, Data Modelling, Security<\/li>\n<li><strong><em>Architects &amp; IT Security<\/em><\/strong> \u2013 who were in terms of organisation line outside ETS but essential contributors in the development eco-system<\/li>\n<li><strong><em>Commercial Management &amp; Support<\/em><\/strong> \u2013 providing vendor relationship management, contract management, sourcing &amp; negotiation and project support (a very limited PMO function, called \u201cAir Traffic Control\u201d at one point, since the development teams were largely responsible for their own progress reporting)<\/li>\n<li><strong><em>The Development teams<\/em><\/strong> \u2013 the main bulk of people, with both generic project teams, and some more specific functions for Security, Treasury systems, LiveFix and .Net (a developing technology practice area, Egg at that time being mainly UNIX based)<\/li>\n<li><strong><em>Solutions Integrity<\/em><\/strong> \u2013 Guardians of quality and the overall integrity of live systems, managing the system test environments and working with the Egg Technology Operations to take systems into live operation<\/li>\n<\/ul>\n<h2>Move to a flex resourcing model<\/h2>\n<p>The major area of difference between the old Egg IT development model and the new Agile arrangement, was in the use of flex resourcing partners.\u00a0 In the old, more corporate structure, most of the people were permanent employees (especially after a temp-to-perm campaign on late 2001\/early 2002), and so there was a high fixed cost.<\/p>\n<p>During the Transformation, the resourcing model changed to a mix of the core permanent development teams, supported by partners who would provide both scale (up to 10x flex), and specialist skills (e..g, IT Security)<\/p>\n<p><a href=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Flex-resourcing-page.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-width: 0px;\" title=\"Flex resourcing page\" src=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Flex-resourcing-page_thumb.jpg\" alt=\"Flex resourcing page\" width=\"754\" height=\"503\" border=\"0\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Partnership Model<\/h2>\n<p>As already discussed, partners were an important part of the resourcing mix, not just for cost reasons, and had some key expectations of them:<\/p>\n<ul>\n<li>Augment our capability<\/li>\n<li>Provide scale and flexibility<\/li>\n<li>Add breadth of expertise and skill (supplement and augment)<\/li>\n<li>Deepen pool of experience<\/li>\n<li>Challenge how we do things \u2013 feedback\/mentor<\/li>\n<li>Are in context with Egg<\/li>\n<\/ul>\n<p>This last point was especially important as it was essential for partners to be able to interact with and be like Egg People.\u00a0 Indeed, in order to maintain the level of Agility the Agile people criteria was used as part of the process by which partner people were evaluated for the suitability to work as part of the Egg agile teams.<\/p>\n<p>As an aside, having a generally compatible culture was an absolute requirement for any aspiring Egg partner \u2013 the counter-case example being Midlands development firm, Zeda <em>[also now departed this mortal coil, having closed in 2008]<\/em>,\u00a0who being more used to Government and Police contracts mistakenly entertained the Egg team to a slap-up meal in the grand dining room of their vast Nottinghamshire mansion headquarters \u2013 and were unceremoniously dinged from the partner selection process for being so out of culture!<\/p>\n<p>The diagram below lays the structure of the partnership model.\u00a0 At the core are the Egg people, who create unique solutions with high customer interaction and significant customer experience component, and the main generators of Egg IP and users of the latest (exciting) technologies;\u00a0 on-site off-site partners, who are like Egg People and supplement them; off-site partners who work on developments which have lower customer experience content, and more routine development that can be well specified in advance; and suppliers, who are not partners but arms-length vendors who provide commodity items and non-unique solutions.<\/p>\n<p><a href=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Partners.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-width: 0px;\" title=\"Partners\" src=\"http:\/\/agile-egg.com\/wpagile\/wp-content\/uploads\/2016\/02\/Partners_thumb.jpg\" alt=\"Partners\" width=\"754\" height=\"503\" border=\"0\" \/><\/a><\/p>\n<p>Next&#8230;<\/p>\n<ul>\n<li><a href=\"http:\/\/agile-egg.com\/wpagile\/retrospective\/\">Retrospective<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The story about the organisation is actually quite short due to their relatively simple design \u2013 it is all about teams The ETS organisation shape iterated from the early start like this\u2026 \u2026to this In all not that much difference between the two,&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":35,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"ngg_post_thumbnail":0,"footnotes":""},"class_list":["post-264","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/pages\/264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/comments?post=264"}],"version-history":[{"count":8,"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/pages\/264\/revisions"}],"predecessor-version":[{"id":579,"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/pages\/264\/revisions\/579"}],"up":[{"embeddable":true,"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/agile-egg.com\/wpagile\/wp-json\/wp\/v2\/media?parent=264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}