tag:blogger.com,1999:blog-7998720216097566103.post5047592382871019712..comments2023-08-04T06:26:13.044-06:00Comments on Lean Technology Transformation: Leveraging Agile Principles in IT Operations: 2 of 4Patrick Phillipshttp://www.blogger.com/profile/16604308740916026438noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-7998720216097566103.post-38943644527761147322011-03-23T15:19:23.126-06:002011-03-23T15:19:23.126-06:00Yuval -- I just found your comment caught in our s...Yuval -- I just found your comment caught in our spam filter. Sorry about the delay! I'll have to keep a closer eye on that.<br /><br />You gave some excellent examples on documentation integration. After posting, I had a conversation about a similar approach with one of the DBA's I work with. <br /><br />After deciding what documentation is valuable, I think the real key is to make it is both relevant and intuitively accessible.Jen Stone Brownehttps://www.blogger.com/profile/13283441553024284549noreply@blogger.comtag:blogger.com,1999:blog-7998720216097566103.post-40654904643752102942011-03-17T15:04:02.563-06:002011-03-17T15:04:02.563-06:00Thanks, Andre! You're making me blush. Tal -- ...Thanks, Andre! You're making me blush. Tal -- I posted that on my wall. Churchill's pithy comments are brilliant.<br /><br />Mike, you make a good point. The concept of working with the business as equal partners is a frustrating one for me, for several reasons. <br /><br />First, the definition of "partnering with the business" seems to vary widely from person to person and company to company. <br /><br />Second, helping the business to understand the value of partnering with IT is a constant uphill battle. I'm working on a way to demonstrate tangible benefits to partnership.<br /><br />Third, the logistics behind partnership are daunting. In what meetings and at what decision-making levels do IT team members need to be available to the business? <br /><br />I've heard CIOs say that attempting to partner with the business is a waste of time, is key to success, is impossible, is simply a catch-phrase, is integral to every project IT takes on. <br /><br />I don't have a good recommendation for partnering with the business, yet, but I'm not letting the concept drop off my radar until I do.Jen Stone Brownehttps://www.blogger.com/profile/13283441553024284549noreply@blogger.comtag:blogger.com,1999:blog-7998720216097566103.post-25298753565002993302011-03-14T20:08:16.350-06:002011-03-14T20:08:16.350-06:00I do not recall where I read an article so precise...I do not recall where I read an article so precise regarding the documentation within Agile. Well done!Andre Andreazzinoreply@blogger.comtag:blogger.com,1999:blog-7998720216097566103.post-18408882576319027612011-03-14T08:34:05.599-06:002011-03-14T08:34:05.599-06:00Nice work! Its great to be clear on the reason for...Nice work! Its great to be clear on the reason for documentation (well done), but until IT management addresses the root cause of daily firefighting and reactive behavior, documentation will always take a back seat. This can only be accomplished working with the business as equal partners.Mike Orzenhttp://www.steadyimprovement.comnoreply@blogger.comtag:blogger.com,1999:blog-7998720216097566103.post-75969144485454215552011-03-13T03:40:30.337-06:002011-03-13T03:40:30.337-06:00I think Winston Churchill said it best: “The lengt...I think Winston Churchill said it best: “The length of this document defends it well against the risk of its being read.”Talhttps://www.blogger.com/profile/12580618246779077331noreply@blogger.comtag:blogger.com,1999:blog-7998720216097566103.post-72210497616319874542011-03-13T03:10:22.803-06:002011-03-13T03:10:22.803-06:00Nice post.
To take something from the dev world -...Nice post. <br />To take something from the dev world - documentation integrated to the code...<br /><br />Examples: <br />- Entities in the Active Directory self-documenting. <br />- Policies in the firewall are named in a way someone understands. <br />- Less numbers, more intelligible names everywhere<br />- wizards that guide you thru troubleshooting, not via word documents or sharepoint sites, but actually allowing you to do stuff to your IT environment. <br /><br />I recall an IT client (major metro in Israel) where the Security Director was upset that not all security procedures were read by new employees. Find the top 3 procedures you really care about and find ways to integrate them into the work. Can even consider this a backlog - prioritize the value from this documentation actually being available, the effort to make it available in a way it will actually be used/consumed, then use it to drive a documentation task force, or as work items that your IT team can do to fill in slack when they are currently meeting SLAs, or when a bottleneck is stopping them. <br /><br />Beyond that I would recommend considering how documentation is helping the organization generate more throughput (cases solved per day?). Find the documentation that will drive the most throughput and focus on that. (TOC...)yuvalhttp://yuvalyeret.comnoreply@blogger.comtag:blogger.com,1999:blog-7998720216097566103.post-89270713706762655102011-03-11T22:10:20.870-07:002011-03-11T22:10:20.870-07:00Thanks, Matt! I hope it helps create positive chan...Thanks, Matt! I hope it helps create positive change that supports your documentation efforts.Jen Stone Brownehttps://www.blogger.com/profile/13283441553024284549noreply@blogger.comtag:blogger.com,1999:blog-7998720216097566103.post-67469866087796563132011-03-11T21:47:38.476-07:002011-03-11T21:47:38.476-07:00This is exactly what we have been trying to do in ...This is exactly what we have been trying to do in our documentation Task force at work. I really like the 4 areas that documentation will be used. I am going to share it. Thanks good stuff!Matthttps://www.blogger.com/profile/09762289539418670053noreply@blogger.com