Components of competency based management

HR infographics "Components of competency based management" was redesigned from the Wikipedia file: Competency-circle.jpg. [en.wikipedia.org/ wiki/ File:Competency-circle.jpg]
This file is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. [creativecommons.org/ licenses/ by-sa/ 3.0/ ]
"Competency-based human resources planning serves as a link between human resources management and the overall strategic plan of an organization. Competencies are defined as observable abilities, skills, knowledge, motivations or traits defined in terms of the behaviours needed for successful job performance.
Competency-based management supports the integration of human resources planning with business planning by allowing organizations to assess the current human resource capacity based on their competencies against the capacity needed to achieve the vision, mission and business goals of the organization. Targeted human resource strategies, plans and programs to address gaps (e.g., hiring and staffing; learning; career development; succession management; etc.) are then designed, developed and implemented to close the gaps." [Competency-based management. Wikipedia]
The HR infographics example "Components of competency based management" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the HR Flowcharts solution from the Management area of ConceptDraw Solution Park.

The vector stencils library "Scrum artifacts" contains 52 icons.
Use this clipart set to design your agile software development diagrams and infographics with ConceptDraw PRO software.
"Product backlog
The product backlog comprises an ordered list of requirements that a scrum team maintains for a product. It consists of features, bug fixes, non-functional requirements, etc.—whatever must be done to successfully deliver a viable product. The product owner orders the product backlog items (PBIs) based on considerations such as risk, business value, dependencies, and date needed. ...
Sprint backlog
The sprint backlog is the list of work the development team must address during the next sprint. The list is derived by the scrum team selecting product backlog items from the top of the product backlog until the development team feels it has enough work to fill the sprint. This is done by the development team asking "Can we also do this?" and adding product backlog items to the sprint backlog. The development team should keep in mind its past performance assessing its capacity for the new sprint, and use this as a guide line of how much "effort" they can complete.
The product backlog items may be broken down into tasks by the development team. Tasks on the sprint backlog are never assigned; rather, tasks are signed up for by the team members as needed according to the set priority and the development team member skills. This promotes self-organization of the development team, and developer buy-in. ...
Sprint burn-down chart
The sprint burndown chart is a public displayed chart showing remaining work in the sprint backlog. Updated every day, it gives a simple view of the sprint progress. ...
Release burn-down chart
The release burndown chart is the way for the team to track progress and provide visibility. The release burndown chart is updated at the end of each sprint by the scrum master. The horizontal axis of the release burndown chart shows the sprints; the vertical axis shows the amount of work remaining at the start of each sprint." [Scrum (software development). Wikipedia]
The clip art sample "Design elements - Scrum artifacts" is included in the Scrum solution from the Project Management area of ConceptDraw Solution Park.