Asif Gill Blogs

Information or data strategy is a part of the overall corporate or business strategy. Information (including data) is an important strategic business asset. Thus, information assets should be managed and treated in the similar way as we manage other business assets. An actionable information strategy is required to for the effective handling of information across the enterprise, irrespective of their size, for achieving the business goals and reducing risk including compliance to regulatory requirements and standards.   This post provides and discusses a simple and practical template for defining the information strategy as a part of the business or cooperate strategy. Information strategy can be defined at the ecosystem, enterprise, business function, business area or capability level as appropriate to your context and needs. Information strategy has following key 8 elements (Figure 1): Mission & Vision, Levers & Value Driver, Goals & Objective, Strategies & Tactics, C

A Theory of Information Trilogy for Information Ecosystem by Asif Gill Information is/of Everything (IioE) We hear many definitions of information and related concepts such as data, information itself, knowledge and intelligence. Well, all these definitions seem useful from information probability, quantification, measurement, storage, processing and management perspective. We still wonder what is "it" and how to identity "it", which we call "information". This blog defines and describes nature ecosystem inspired definition of information, which is called here a "Theory of Information Trilogy" (ToIT).  This theory is defined with a view to define and identify information in complex and heterogenous information ecosystems.  This theory defines that the information is (1) matter and (2) energy, which has different (3) states or forms. Matter and energy flow in the natural ecosystem. Further, from natural ecosystem, these 3 matter, energy and their

Agile processes are often considered challenging to adopt in larger and formal project development and management environments. It may not be possible and need for an organisation to adopt a pure agile process for a large project. How can organizations adopt agile planning and estimation best practices within their formal and generic process lifecycle (GPL)? This article presents an agile planning and estimation model that can be used for large projects as a guide. Agile Process The core of the agile process is a collection of sprints or small increments. The agile process can be classified into three key categories or stages: ·        Pre-Sprint – focus on the analysis activities of the GPL ·        Sprint – focus on the planning and development activities of the GPL ·        Post-Sprint – focus on the sprint post-mortem and release activities of the GPL.   The agile process has practices that can be executed within a GPL to produce the specific project deliverables. The