- Docker and Kubernetes: Major software vendors are now using Docker and . Kubernetes is an open-source container-orchestration system for automating deployment, scaling and management of containerized applications. It was originally designed by Google and is now maintained by the Cloud Native Computing Foundation. This means that you don’t need VMWare and probably won’t need Linux or Windows licences. Vendors ship their software in Docker contains which are preloaded, preconfigured with Ubuntu and all the software stack. The host is controlled by Kubernetes. This is a great way to roll out patches. One speaker from IBM claimed that they can now patch complex systems in minutes rather than hours. RedHat have OpenShift which is an alternative to Kubernetes.
- GDPR: 80% of companies don’t think they will be fully GDPR complaint before the end of 2018 – it’s a long journey and to a large extent it’s never complete and has to become Business As Usual.
- “Compressing time to value“, this can be achieved through Self Service Applications and Automation.
- “Continual Touch“, this is a business model objective where you try to be constantly working in partnership with your customer to provide a service. It’s an extension of cloud and SaaS (annuity model hosting).
- “TIM WOODS“, I’ve read a lot on Lean-Agile over the years but somehow this brilliant acronym hadn’t come to my attention. It spells out the areas where waste happens in a business.T – Transport – Moving people, products & information
I – Inventory – Storing parts, pieces, documentation ahead of requirements
M – Motion – Bending, turning, reaching, lifting
W – Waiting – For parts, information, instructions, equipment
O – Over production – Making more than is IMMEDIATELY required
O – Over processing – Tighter tolerances or higher grade materials than are necessary
D – Defects – Rework, scrap, incorrect documentation
S – Skills – Underutilizing capabilities, delegating tasks with inadequate training
- Security concepts – “Session Break” and “Secure Proxy”: These are useful concepts for keeping backend systems secure. Session Break means that a process can’t talk directly end to end to achieve a given outcome. For example, a customer might place an order via a website. Instead of having the website write the order directly to the fulfilment system it places an XML or JSON representation of the order on a file server. An entirely separate process then picks up any new order files. This helps protect the backend fulfilment database as the web application doesn’t have any access to that database. Secure Proxy is similar, it means that external users login to an application using a set of user credentials that are only valid on the proxy itself. The proxy then forwards requests to the backend or maps the external user to an internal user. This again protects the backend application.
By Gayle Laakmann McDowell published by CareerCup
This looks like a really useful book for new developers attending job interviews. I think it’s also useful if you are responsible for recruiting and interviewing developers. I wouldn’t suggest using any of the examples given in this book in an actual interview for obvious reasons but having seen the style you can create your own similar questions. In my experience if you do this then it’s essential to test the questions on a few of your existing developers to benchmark the questions and see what good looks like.
Click here to view this on Amazon.co.uk
One of my most popular blogs last year was my UK Minutes Template. At the time I just wrote about a Minutes Template that I’ve used a lot over the years but I’ve got lots more examples that may be more appropriate to different styles of meeting. Over the coming weeks I plan to compile a few more example templates for meeting minutes and write a follow-up blog. I’d love to hear from you if you’ve got a great meeting minutes template that you’d like to share. I’m happy to edit any templates you send over to remove company details and make them generic.
I’d also love to know what formats best suit people, I’m assuming Microsoft Word but may be people are increasingly using Apple Pages or Google Docs.
I’ve been using Twitter client sites for years now but never got around to setting it up for my own IT blog. This evening I have finally created a Twitter Account to go with this blog. If you follow ITMAN101 on Twitter I’ll let you know whenever we post a new blog or have any news to share.
Here’s our very first tweet…
— ITManagement101 Blog (@ITMAN101) January 4, 2016
Definitions: Service Assets: Resources & Capabilities
Resource: IT equipment / infrastructure, people, money or anything else that helps to deliver the service. Resources are assets of the organisation.
Capability: The ability of a service organisation, person, process, application or IT service to carry out an activity. Capabilities are intangible assets such as management, organisation, process, knowledge and peoples skills.
The diagram above shows all the elements that come together to create an IT Service. These are detailed below.
- Business Processes: Examples include Order Entry and Credit Checking
- Service: The service being delivered to customers for example Billing
- Service Design Package (SDP): A package of documents defining all aspects of a service and its requirements through each stage of its lifecycle.
- Business Case: The justification for the service investments and expenditure
- Service Level Agreements (SLAs) and Service Level Requirements (SLRs): Set out the level, scope and quality of the service that is to be provided.
- Infrastructure: All the IT equipment required to deliver the service.
- Environment: When the IT equipment is securely implemented, typically data centres, machine rooms, power, cooling etc.
- Data: The data required to provide the service. For example customer records, product records, supplier details etc
- Applications: All the software required to process the data to provide the information required by the business process for example ERP packages, CRM packages etc.
- Integration: Solutions to integrate/combine data from different sources.
- Operational Level Agreements (OLAs) and Contracts: Any underpinning agreements required to deliver the service within the SLA.
- Supporting Services: Any services required to deliver this service – e.g. Networking.
- IT Processes: The processes needed by the service provider to ensure the successful delivery of the service for example Service Desk Management, Change Management, Availability Management, Monitoring etc.
- Functions: Any internal teams providing support for any of the components required to provide the service, for example Service Desk.
- Roles: Responsibilities, activities, authorities granted to a person or team that control and deploy the resources engaged in the service. For example Problem Managers, Release Managers, Capacity Managers and Service Owners.
- Suppliers: Any external third parties necessary to provide the service. For example the Internet Service Provider would be a key supplier for a Web Service.
ITIL Service Management defines a number of terms, this primer is a quick reference guide. You should find this useful when revising for your ITIL Foundation Exam.
Outcome: The output from executing a process that delivers a SERVICE
Service: A way of delivering value to a customer by enabling an Outcome the customer wants to achieve without incurring the overhead of owning the whole process or risks of delivering it.
IT Service: Delivered by an IT Service Provider. It is a combination of technology, people and processes.
There are 3 types of Service:
- An internal customer facing service: IT Service provided to another part of the same company.
- An external customer facing service: IT Service provided directly to an external customer, for example a music download service.
- A supporting service: A service which is not directly used by the business or an external customer but which is required by the IT Service provider to deliver other services, for example backup and recovery.
These service types can be further sub-defined as:
- Core Services: These are the (top level) services that would be recognised by the customer as the service they are paying for.
- Enabling Services: These are services needed to deliver Core Services. They may be visible to customers but are not sold to them in their own right.
- Enhancing Services: Think of these as “Core Services Plus”. They are not essential to delivering the Core Service but are extras used to differentiate the service from its competitors
Service Package: A bundle of two or more services (could be core, enabling or enhancing) designed to meet a specific type of customer requirement or to underpin a specific business outcome.
Service Value: Customers cannot benefit from something that is fit for purpose but not fit for use and vice versa. What’s the point of having a fantastic helpline if its always engaged when you phone it. Service Value therefore breaks down into Utility and Warrenty.
- Utility – What the service gives the customer – it’s fitness for purpose. Think of this as the functionality provided by a product or service to meet a particular need. In my example a helpline that will be able to answer any technical question.
- Warranty – How it is delivered – it’s fitness for use, eg sufficient capacity, availability, security etc. This is the assurance that the product or service will meet its agreed requirements. This may be expressed formally in an SLA. In my example the helpline will be open 24 hours a day and the call will be answered within 30 seconds.