Skip to content. | Skip to navigation

Personal tools

Reference and guide to SFIA version 7. Framework status: Current standard.

Archived change requests

RSS feed

These are the change requests which were submitted and acted upon during the SFIA 7 revision process (July 2017 to April 2018). Some of the change requests were accepted, some rejected ans some deferred for the next revision cycle. The text and history of each request is in this section. The deferred change requests are still active and can be seen and discussed in the ‘Future SFIA’ section.

Search change requests

  • Accepted (88)

  • Declined (11)

  • PRMG - make inclusive to plan-driven and adaptive (iterative/agile) methods 0 #1271 15 May 2018

    Need to recognise that different projects / programmes require different approaches. So the skill should include reference to adopting and adapting PM approaches based on the context of the work and selecting appropriately from plan-driven/predictive approaches or more adaptive (iterative and agile)…

    What we decided:

    Accepted.

  • ARCH - check references to systems architectures 1 #1264 11 Apr 2018

    DESN has been rewritten to ensure that it has a focus on broad concept of systems design. i.e. It does not imply a Business solutions focus. Whereas Solution Architecture can be focused on Business solutions - so should it refer to Systems Architecture? or Solution Architecture?

    What we decided:

    Accepted.

  • PROD typo 0 #1262 4 Apr 2018

    Need to remove the word "a" from the overall description not that it talks about "products or services".

    What we decided:

    Accepted.

  • BUAN - make inclusive to both plan-driven and iterative methods 0 #1261 28 Mar 2018

    Need to recognise that different projects / programmes require different approaches to how they perform business analysis work. So the skill should include reference to adopting and adapting business analysis approaches based on the context of the work and selecting appropriately from plan-driven/pr…

    What we decided:

    Accepted.

  • ITSP - consider name change to broaden use and acceptability. 0 #1259 22 Mar 2018

    The skill was originally called IT Strategy and planning. With the ever closer relationship between "business " strategies and "IT" or "technology" strategies should we remove the IT prefix.

    What we decided:

    Accepted.

    Note just removing IT as a prefix would leave the skill called "Strategy and planning" - suggest Strategic planning as an alternative.

  • DTAN - consider name change to Data modelling and design 0 #1258 22 Mar 2018

    DTAN current describes Data analysis activities which are part of the systems development life-cycle, e.g along side business analysis. In the industry the term Data Analysis is also applied to data analytics - which is described in the SFIA skill called "Analytics". A name change will be helpful to…

    What we decided:

    Accepted.

  • SORC - separate out supplier management activities 0 #1257 22 Mar 2018

    Consider the implications of change request #40. If we create a "supplier management" skill then elements of the current SORC descriptions should be extracted and move to the new skill.

    What we decided:

    Accepted. Dependent on decision on supplier management and relationship management.

  • INAN - consider need to seprate out Analytics from Visualisation 0 #1256 22 Mar 2018

    INAN includes elements of data visualisation. Feedback suggest that the industry has roles which may specialise in one or the other of data analytics and data visualisation. If visualisation is just the "press of a button" and the analytics tool does it for you then that should remain combined with…

    What we decided:

    Accepted. But note that for this to be viable addition it needs to be more than “uses the chart function in Excel” or uses in-built visualistion tool in analytics platforms.

  • BPRE - refresh language and scope to cover relevance to digital transformation 0 #1255 21 Mar 2018

    Many digital transformation initiates and programmes focus on re-engineering, re-thinking business processes. The use of new digital technologies allows enterprises to transform their existing business activities and also allows new organisations to change industries by exploiting disruptive technol…

    What we decided:

    Accepted.

  • SUAS - retire Sustainability assessment 0 #1254 21 Mar 2018

    See change request #42 Revisit the need for the 4 Sustainability skills.

    What we decided:

    Accepted.  As part of overall rationalisation of sustainability related skills in SFIA.

  • SUMI - retire Sustainability management 0 #1253 21 Mar 2018

    See change request #42 Revisit the need for the 4 Sustainability skills.

    What we decided:

    Accepted.  As part of overall rationalisation of sustainability related skills in SFIA.

  • SUEN - retire Sustainability engineering 0 #1252 21 Mar 2018

    See change request #42 Revisit the need for the 4 Sustainability skills

    What we decided:

    Accepted.  As part of overall rationalisation of sustainability related skills in SFIA.

  • STMG - align level 6 skill with DATM 0 #1251 19 Mar 2018

    SFIA6 STMG level 6 included wording " Drafts and maintains policies and standards for the corporate data management practice and align storage investments and data management policies". Policies for corporate data management are already described in DATM so we should remove duplication while recogni…

    What we decided:

    Accepted. Review as part of overall refresh of Big Data and Informatics related skills in SFIA.

  • USEV - review and refresh language and activities described 0 #1250 19 Mar 2018

    User experience analysis and user experience design have both been refreshed. In addition a new skill User research is proposed. USEV should be reviewed and refreshed to ensure the suite of UX related skills are consistent and compatible.

    What we decided:

    Accepted.  Changes must be considered alongside the other UX related skills.

  • CSMG - make inclusive to broader range of customer service delivery channels 0 #1249 17 Mar 2018

    CSMG - refresh language to make explicitly inclusive to broader range of customer service delivery channels including human, digital, self service and automated.

    What we decided:

    Accepted. One of a number of skill updates to support broader inclusion and for digital transormation and digital service provision.

  • INOV - refresh language and levels 0 #1248 11 Mar 2018

    INOV - refresh language and levels to reflect importance of inovation to digital transformations. Consider level 7 to provide strategic leadership to drive organisation wide approach and culture for innovation.

    What we decided:

    Accepted. Should be reviewed alongside the other Digital Transformation skills and related change requests.

  • Minor levels of responsibility changes 0 #1247 7 Mar 2018

    Ensure generic levels of responsibility apply across the whole organisation

    What we decided:

    Accepted.

  • UNAN - reinforce experience design is inclusive of products, systems, services 0 #1246 28 Feb 2018

    Over use of the word "system" in the skill level descriptions - instead of being consistent with the first reference in the overall skill description to"products, systems, services". Level 3 & Level 4 overuse examples which broadly should be avoided where they can lead to the reader forming a t…

    What we decided:

    Accepted - and should be reviewed alongside the other User Experience related skills.

  • CSMG - A typo that doesn't appear as a typo 0 #1244 23 Feb 2018

    Customer Service Support (CSMG), Level 3: replace "development standards" with "development of standards".

    What we decided:

    Accepted as a straightforward requirement with no impact on other skills.

  • DBAD - consider any implications of DevOps and automation 0 #1242 11 Jan 2018

    We should review the skill & skill level definitions associated with database administration to consider any updates required to ensure configuration of (populated) database environments for testing, quality assurance.

    What we decided:

    Accepted. Ensure consistency with other related skills in the Devops lifecycle.

  • RLMT - more emphasis needed on Supplier (Relationship) Management 0 #99 2 Jan 2018

    Change Request raised on behalf of itSMF International via Barry Corless (Director - itSMF International) Supplier (Relationship) Management seems to fall between the cracks in the current version of SFIA. The advent of (and growth in popularity) of Service Integration and Management (SIAM) adds…

    What we decided:

    Accepted. Additional skill Supplier management (SUPP) included in SFIA7.

  • Knowledge Management - new skill? 1 #98 2 Jan 2018

    Change Request raised on behalf of itSMF International via Barry Corless (Director - itSMF International) Needs to be called out as a specific skill set(s) Thought needs to be given to the full cycle of skills from strategy through the key steps; identifying, capturing, verifying, storing, disse…

    What we decided:

    Acccepted.

    NB But we need to be careful this does not imply a skill every role should have - e.g. if part of your job requires you to update the KM database then thats not a knowledge management skill that is recording data . KM is concerned with moving from Data to Information to Knowledge [to Wisdom] and then making decisions and taking action.  

    I think KNOW is complementary to IRMG. So in a Venn diagram we would see a degree of overlap. But that doesn’t mean we should collapse Knowledge management into Information management. Neither should we imply or specify an organisation / role design by saying if you do Knowledge management you also do Information management.

    A lot of knowledge management relies on fuzzier and social constructs (e.g. communities of practice, story telling, as well as a systematic approach.

  • CPMG - more focus on service design 0 #97 2 Jan 2018

    Change Request raised on behalf of itSMF International via Barry Corless (Director - itSMF International) The current skills does not provide enough emphasis on the role of designing in capacity at all.

    What we decided:

    Accepted.

  • Demand Management - new skill? 0 #95 2 Jan 2018

    Change Request raised on behalf of itSMF International via Barry Corless (Director - itSMF International). Demand Management (in terms of predicting from the business / customer demand) isn't really covered adequately.

    What we decided:

    Accepted. Some knock on effects to Requirements defintion and management and Capcity management.

  • PROD - downplay sales & marketing references 1 #94 30 Dec 2017

    The Product Management (PROD) skill could be reused across a variety of roles (e.g. in agile team, or in Service Management) if the references to sales and marketing weren't quite so strong.

    What we decided:

    Accepted.

  • QUAS - revise lv3 skill level description 0 #93 30 Dec 2017

    QUAS3 reads like QUST. Should be closer to CORE3.

    What we decided:

    Accepted. As part of wider review of the quality related skills.

  • PEMT - Remove reference to change and/or service delivery environments 0 #92 30 Dec 2017

    Not sure why PEMT6 references managing individuals within change and/or service delivery environments!?

    What we decided:

    Accepted. ee "What we Changed" section for details.

  • SINT - check lv3/4 descriptions 0 #91 30 Dec 2017

    The overlap between the skill level descriptions for SINT3/SINT4 make it hard to separate out the levels. Arguably the only real difference is the inclusion of "moderately complex problems" in level 3.

    What we decided:

    Accepted. See change reques #16.

  • HCEV - seperate the skill from the job 1 #90 30 Dec 2017

    Skill level descriptions for User Experience Design (HCEV) can read like a complete (and quite expansive job) rather than an individual skill.

    What we decided:

    Accepted - and should be reviewed alongside the other User Experience related skills.

  • Seperate STPL6/BUAN6 skill level descriptions 0 #89 30 Dec 2017

    Remove duplicate text in STPL6/BUAN6

    What we decided:

    Accepted.

  • TECH - clean up lv4/lv5 skill level descriptions. 0 #88 30 Dec 2017

    Remove "The specialism can be any area of information or communication technology, technique, method, product or application area." If this is really needed, then add to the overall description.

    What we decided:

    Accepted. See "What we Changed" section for details.

  • MKTG - Revert to Marketing instead of Digital Marketing 0 #87 30 Dec 2017

    SFIAv6 description makes this skill seem very limited to digital marketing, leaving a gap that the v5 description of Marketing seemed to fill.

    What we decided:

    Accepted.

  • INCA - change examples to be less website-centric 0 #86 30 Dec 2017

    Make the examples given in INCA less website-centric through use of other examples … Content Authoring is used in a wide variety of contexts.

    What we decided:

    All skill levels and overall skill description have been updated.

  • IRMG - Rename to Information Governance 0 #83 30 Dec 2017

    Consider renaming IRMG from Information Management to Information Governance.

    What we decided:

    Accepted.

  • GOVN - 0 #82 30 Dec 2017

    Expand to cover the broader view of EIT Governance (reference the ISACA CGEIT materials COBIT model). Name change to Enterprise IT Governance.

    What we decided:

    Accepted.

  • GIS 0 #81 22 Dec 2017

    Adding a skills around using and maintaining a GIS systems, using as tool for problem solving and decision making processes. using for visualization of data in a spatial environment such as an asset management system.

    What we decided:

    Accepted. See "What we Changed" section for details.

  • EMRG - add reference to technology roadmaps 0 #76 7 Dec 2017

    Technology road mapping is a well-established concept/technique relevant to technology assessments. Suppliers and product providers also publish their own product strategies and road maps. Reference to roadmaps and roadmapping in EMRG will ensure the focus is not just a "point in time " assessment.

    What we decided:

    Accepted.

    Note include the fact that EMRG needs to consider that many disruptive technologies which are a threat to current industry players.

  • Incident Investigation 0 #74 6 Dec 2017

    Abbreviated version of SCTY407 needed in SCTY3

    What we decided:

    Accepted.

  • The skills needed for skills assessment 0 #71 30 Nov 2017

    The skill associated with "skills assessment" is tucked away under Learning assessment and evaluation. However skills assessment is frequently performed in other contexts e.g. workforce planning, performance conversations, capability improvement, organisation design.

    What we decided:

    Accepted.

  • GOVN - update IT governance descriptors 0 #70 30 Nov 2017

    The role of IT governance becomes more into the foreground during the design and implementation of new IT operating models. E.g. related to outsourcing or service integration developments. More focus could be given to ensuring there is a focus on value of governance and that it included the opera…

    What we decided:

    Accepted. See change request #70.

  • User experience 1 #66 26 Nov 2017

    Consider developing the criteria of this skill to incorporate more from disciplines of Ethnography, Human centred design and Design thinking. e.g.: https://aliciadudek.wordpress.com/what-is-a-design-ethnographer/ http://www.designkit.org/human-centered-design Review the User centred design roles …

    What we decided:

    Accepted. Solution must be developed alongside the 3 UX skills in SFIA v6 and the RSCH skill.

  • COPL - Review level descriptions 0 #65 23 Nov 2017

    Continuity planning has SFIA Level 4 and 5 but is fully described at Level 5 only.

    What we decided:

    Accepted.

  • DBDS Database Design - Insufficient distinction between level descriptions 0 #64 23 Nov 2017

    The wording in Database Design skill-level descriptions is too similar for levels 3, 4 and 5. It is difficult when assessing against this skill, or when considering the skill for a role-profile, to gauge what level is relevant.

    What we decided:

    Accepted. Note that by removing level 6 and clarifying differences between levels this is likely to impact skills assessment processes.

  • Service Improvement an explicit skill 1 #62 9 Nov 2017

    Introduce a Service Improvement skill

    What we decided:

    Accepted.

  • STPL - Enterprise & business architecture 0 #60 8 Nov 2017

    STPL Skill description for Level 6 - make the main points first.

    What we decided:

    Changes to level 6 made as described.

  • TMCR - Learning design and development. 0 #59 8 Nov 2017

    The v6 skill-level descriptions for TMCR are each 1 level too high

    What we decided:

    Accepted. Note this will have some impact on SFIA skill assessments.

  • IT Infrastructure - bring up to date 2 #55 31 Oct 2017

    Update old language to reflect current views on infrastructure around cloud services etc.

    What we decided:

    Accepted. Assume standlone change with no imapct on other skills.

  • Digital Forensics - Add 'totality of findings' 0 #52 31 Oct 2017

    The explicit reference to "computer' related evidence is too restrictive and incorrect.

    What we decided:

    Accepted.

  • Ensure SFIA6 Corrections Included 1 #50 31 Oct 2017

    A number of people have commented that there are a number of typos and errors in SFIA6 and these should be corrected.

    What we decided:

    Accepted.

  • Enhance SFIA to address Digital Accessibility Issues 0 #49 19 Oct 2017

    SFIA needs to address the skills needed to develop accessible systems.

    What we decided:

    Accepted.

  • Architecture skills should start at lower level 3 #48 18 Oct 2017

    Users have requested that the architecture skills start at a lower level to reflect 'size' and the difficulty of getting architect skills at L5 so this would reflect a more junior level on an architecture career path - particularly for Solution Architect

    What we decided:

    Accepted.

  • BENM - Benefits management minor changes 0 #47 10 Oct 2017

    The skill description and the skill level descriptions can be improved.

    What we decided:

    Accepted. Minor changes which do not impact elsewhere.

  • Embedded systems and Internet of Things 1 #46 1 Oct 2017

    There is a skill set for those who make and code embedded systems. whether weather stations or drones. They include real time Analog to digital sensing, low-level coding including assembler, but now also IP and networking, RF etc

    What we decided:

    Accepted. See also change request #16.

  • Skills for Research Software Engineers? 0 #45 1 Oct 2017

    Research Software Engineers -AKA science coders. They do stuff like numerical modelling, High-performance computing, algorithm development etc. Currently, there is a single PROG line for coding that covers some non-overlapping capabilities.

    What we decided:

    Accepted.  See "What we Changed" section for details.

  • Revisit the need for the 4 Sustainability skills 6 #42 1 Oct 2017

    In 2010 - 4 sustainability skills were added to SFIA version 4 to create SFIA 4G. This should be revisited with 2 key lines of inquiry. 1 - Should sustainability been seen as a standalone set of skills - or can it be adequately covered in other specific skills? 2 - Do we need 4 separate skills?

    What we decided:

    Accepted. The proposals to rationalise needs to ensure other parts of SFIA cover the content satsifactorily.

  • DLMG - separate out software process improvement 1 #41 1 Oct 2017

    For SFIA6 - software process improvement skill was removed has been merged into systems development management. Why? Many roles focus on software process improvement but not systems development management – they should be separate.

    What we decided:

    Accepted.  See "What we Changed" section for details.

  • RLMT - separate out supplier and stakeholder management skills 5 #40 1 Oct 2017

    SFIA6 merged 2 skills - Stakeholder Relationship Management and Supplier Relationship Management. Although there are similarities - the 2 skills should be de-merged. Going back to the SFIA5 definitions would be a short-cut - but, ideally, both skills should be revisited. Developments of the SIAM mod…

    What we decided:

    Accepted. Solution must also look at impact on Sourcing skill.

  • Measuring Service Performance in a wider context 1 #39 19 Sep 2017

    In government large numbers of users (external - general population) systems need to measured in terms of their performance, not just in terms of service level agreements, but also in terms of user feedback from engaging with the service or product.

    What we decided:

    Accepted as part of a broader need to reflect Measurement skills in SFIA7.

  • Research Skill needs strengthening 2 #38 17 Sep 2017

    It would be good to more clearly distinguish to concept of research in common use of the term (information gathering) and research more directed to creating new knowledge (the definition used in Government funded KTP technology transfer projects and by universities for PhD degrees). Good to distingu…

    What we decided:

    Accepted.

  • How to address Technical Writing skills 0 #37 15 Sep 2017

    A number of user organisations have remarked that there is not a neat match for Technical Writing skills.

    What we decided:

    Accepted. See "What we Changed" section for details.

  • Measurement - Improvements to address needs of Software Engineering 1 #36 8 Sep 2017

    Consider introduction of skill descriptions to support Measurement capabilities. Product and process measurement is a key component of Software Engineering practices; in addition measurement is also of growing importance in other areas of enterprise IT.

    What we decided:

    Accepted as part of a broader need to reflect Measurement skills in SFIA7.

  • Update the Data Skills to reflect new data thinking 3 #34 6 Sep 2017

    Given the increased importance of data in digital transformation, interoperability and 'large data' capabilities and directions a number of data skills need to be revised and enhanced.

    What we decided:

    Accepted. A wide review of all data related skills in SFIA against industry standard frameworks to highlight any gaps and opportunities.

  • Data Science - New Skill? 5 #33 6 Sep 2017

    A new data science skill is required.

    What we decided:

    Accepted. Requirement is to explain which SFIA skills are relevant to Data Scientist role.

  • Data Quality - New Skill? 3 #32 6 Sep 2017

    A new data quality skill is required.

    What we decided:

    Accepted. Data quality should form a part of the Quality skills in SFIA.

  • Data Governance - New skill? 2 #31 6 Sep 2017

    More emphasis on data is required - to reflect current direction of digital transformations.

    What we decided:

    Accepted.

    Requirement is to be clearer how "Data governance" is supported by SFIA.

    Solution is to refresh the SFIA skill defintions and explain how the SFIA skills support Big Data as a whole.

  • Reference Guide Format - Needs to be significantly improved 3 #30 6 Sep 2017

    The reference guide is a vital tool, many still like to work off a book but it is difficult to navigate and some areas need to be enhanced.

    What we decided:

    Accepted.

  • ASMG - extend to lower level 2 #29 6 Sep 2017

    ASMG starts at L4, but activities and work seen at L2 &3

    What we decided:

    Accepted. Expect this to be a stand alone change with no impact on other skills.

  • Generics, Skills and Knowledge - better explanation in Reference Guide 1 #27 6 Sep 2017

    Need to better explain the relationship of generics skills and knowledge. Also need to raise awareness of the importance.

    What we decided:

    Accepted.

  • Skills vs Knowledge guidance - Guidance needed 1 #24 6 Sep 2017

    Need enhanced description of skills vs knowledge

    What we decided:

    Accepted.

  • Capability Improvement - reintroduce updated SPIM and clarify METL 4 #22 6 Sep 2017

    SPIM was removed from SFIA5 - It should be reintroduced and clarification with METL established.

    What we decided:

    Accepted.

  • Real-time Systems Development - Improvements to address needs of Software Engineering 0 #18 10 Aug 2017

    Should real-time systems development be described as a stand-alone, end-to-end skill or is it better positioned as a particular instance of all the software engineering skills?

    What we decided:

    Accepted

  • SINT - Improvements to address needs of Software Engineering 1 #16 9 Aug 2017

    Some changes in emphasis and wording across the Skill description and skill level descriptions to ensure Software Engineering is addressed.

    What we decided:

    Accepted.

  • METL - Improvements to address needs of Software Engineering 1 #15 9 Aug 2017

    Some changes in emphasis and wording across the Skill description and skill level descriptions to ensure Software Engineering is addressed.

    What we decided:

    Accepted.

    Make sure the skill description is agnostice / neutral to what the method or tool is.

    Ensure clearer delineation between levels and that the skill level descriptions have sufficient indicators (SFIA6 version are very short).

  • CFMG - Improvements to address needs of Software Engineering 3 #14 9 Aug 2017

    Some changes in emphasis and wording across the Skill description and skill level descriptions to ensure Software Engineering is addressed.

    What we decided:

    Accepted.

  • PROG - Improvements to address needs of Software Engineering 1 #12 8 Aug 2017

    Some changes in emphasis and wording across the Skill description and skill level descriptions to ensure Software Engineering is addressed.

    What we decided:

    Accepted.  See "What we Changed" section for details.

  • DESN - Improvements to address needs of Software Engineering 2 #11 8 Aug 2017

    Some changes in emphasis and wording across the Skill description and skill level descriptions to ensure Software Engineering is addressed.

    What we decided:

    Accepted.

    Consider whether Software design should be a standalone skill. Check for current usage of System design (DESN) and Solution architecture (ARCH) skills.

  • REQM - Improvements to address needs of Software Engineering 4 #8 7 Aug 2017

    Some changes in emphasis and wording across the Skill description and skill level descriptions to ensure Software Engineering is addressed.

    What we decided:

    Accepted. There are a number of impacts from this change requests. See "What we Changed" section for details.

  • Knowledge needs to be addressed more explicitly 8 #7 5 Aug 2017

    SFIA's position on knowledge while correct does need to be reviewed and enhanced. Few seem to understand the position or why the particular position was taken. Knowledge needs to be revisited and addressed in such a way that it is clearly understood and allows the position to be used effectively.

    What we decided:

    Accepted.

  • Need To Recognise the Roles of Product Owners 5 #5 2 Aug 2017

    The rise of iterative and agile based approach to solution and service delivery has evolved into the cross over of the business sponsor roles and technical delivery assurance practitioners into Product Development owners, specialist and managers

    What we decided:

    Accepted. There are a number of impacts related to this change request. See "What we Changed" section for details.

  • Extend Teaching & Learning Skills to Lower Levels 3 #4 28 Jul 2017

    Suggest defining the teaching and learning skills in SFIA at lower levels, so these equate to practice (at least in Australia). http://blog.highereducationwhisperer.com/2017/07/extend-teaching-skills-for-it-profession.html

    What we decided:

    Accepted - but with a different solution.

    Mentoring has been raised as change request #85.

  • Quality Standards Skill - Needs Reviewing 3 #2 18 Jul 2017

    Aspects of quality are distributed through out skills but there are 4 skills associated with quality including this one, which is not that well defined. Consider merging into Quality Management

    What we decided:

    Accepted. Consider as part of review of all quality related skills in SFIA.

  • Research 0 #1007 2 Oct 2014

    Missing Research and innovation management does not seem to be fully included in SFIA. Presumably the head of Microsoft research would struggle to map their skills to SFIA. How should I map the skills I have in managing researchers working with technology companies to SFIA? Entrepreneurialism in a t…

    What we decided:

    Accepted. See "What we Changed" section for details.

  • Configuration management 0 #1239 2 Oct 2014

    Level 3 – Applies tools, techniques and processes for administering information (such as the tracking and logging of components and changes) related to configuration items. Level 2 - Understands tools, techniques and processes for administering information (such as the tracking and logging of co…

    What we decided:

    Accepted.

  • TECH CONS 0 #1061 2 Oct 2014

    Another example is Technical Specialism or Consultant, these are "catch all’s" and really some is Technical Specialist in X or Y Consultant, and if people call themselves these it is with an emphasis on the X or Y in terms of their development path. 

My focus is for being an assessor in BCS a…

    What we decided:

    Accepted.

  • Data scientist role 1 #1123 2 Oct 2014

    All the above is nothing new though the extent and scale is staggering, the sheer numbers that could become valid applicants under data scientist roles will challenge the understanding of many who may consider these activities as academic as opposed to mainstream or IT.

    What we decided:

    Accepted. As part of broader them of SFIA and Big Data / Informatics.

  • Needs better distinction from innovation 0 #64 8 Jun 2014

    Change wording so that it doesn't read like an alternative description of the "innovation" skillset.

    What we decided:

    Accepted.

  • Technical specialism - change name as not just about technical 0 #21 16 Mar 2014

    The description covers many non-technical aspects, therefore the skill name should be changed. Suggest changing it to "Specialist advice"

    What we decided:

    Accepted.

  • IT Governance - change skill name 0 #15 16 Mar 2014

    Change skill name to "Governance" to reflect common view which sees the IT term as restrictive, particularly for Communications Service Providers, like those in telecoms or in information provision.

    What we decided:

    Accepted. See change request #70.

Navigation