Today was the second and final day of the IT & Enterprise Architecture Conference 2015. Below is a summary of my key notes. Going beyond IT. What EA can really mean for your organisation John Pearson, Business Architect, IAG Consider the Demand vs Supply side of architecture IAG is using traditional TOGAF domains (Information, Application, Technology Infrastructure and Security) with business architecture being used to better align with the demand from the business Enterprise Business Motivation Model (EBMM) - Accenture, Nick Malik ( http://www.motivationmodel.com/ ) anchor diagram for business architecture using to understand change impact Bake business architecture approaches in early in the architecture journey Understand the business, its priorities and where value can be added Understand architecture capabilities in service to the business Understand key stakeholder needs and communication preferences Become involved in the strategy conversation Technol
Having been on the receiving end of Request for Information (RFI) and Request for Proposal (RFP) responses, from an evaluation perspective there are ways respondents can make it easier for the evaluation panel to assess what it is being proposed and ultimately have greater success on getting through to the next round. These considerations are from my experiences with Software package selection and with Delivery partner selection, but should be applicable to many other selections. 1. First impressions count. Even before the RFI/RFP response is opened, an evaluator can be swayed by the presentation of the response and the level of engagement getting there. Key considerations: Ask questions during the response period to validate any areas lacking clarity, but don’t go overboard. Make sure you meet the response times. Use good quality paper and colour (if required to present a paper copy). Binding can make a document look classier. If the response requests that all questions a
A colleague was noting that he was wanting a better approach to manage his email so I thought I should document what I have been doing for several years now and has been (mostly) working for me. The general concept is that I aim to have nothing in my Inbox at the end of each day. The approach I have been using builds on top of Getting Things Done (GTD) , Inbox Zero and the Eisenhower Matrix to prioritise it. Ideally as soon as an email arrives and I get around to looking at, I move it to an appropriate folder to action later, respond straight away, file it away in my archive folders or delete it. In reality I often end up going through what is still lingering in my Inbox at the end of the day and do this. I have some key folders setup: 1. Action - Urgent and Important 2. Action - Urgent but not Important 3. Action - Not Urgent but Important 4. Action - Not Urgent and Not Important Casual Reading These are the key folders I use for determining the priority of actioning an incoming
Comments
Post a Comment