#NAME?
Agile Delivery Delivery
Broad Definition:
This competency refers to the ability of the associate to understand and apply Agile values, principles, frameworks and practices in their projects.
Criteria
E0
E1
E2
Not applicable
Should have acquired E0 proficiency
Should have acquired Should have acquired E1 proficiency E2 proficiency
Note : This level could be mapped to Developer role
Note : This level could be mapped to Agile Facilitator/Scrum Master, Product Owner and Developer
E3
E4
I Criteria for defining proficiency vis-à-vis knowledge & skills 1. Precondition [Expressed as a prerequisite - in terms of academic qualification qualification AND / OR industry experience (whichever is applicable) AND / OR relevant knowledge in any other competency]
Note : This level could be mapped to Developer role
Should have the Should have knowledge of 2. Knowledge knowledge of : Agile Engineering Engineering practices practices [Expressed as Area of knowledge and not skill, 1. Agile values and such as principles as Clean Code (Source Code includes knowledge of Control, Coding Standards, process, methodologies, methodologies, described in the Agile Manifesto Manifesto Peer Review, Collective Code concepts and tools] 2. Should be aware ownership, Code quality, Pair of basic Agile Programming and Unit frameworks and be Testing) able to differentiate Emergent design (Refactoring between them and Test Driven Development) 3. Should have the Testing and Automation knowledge of the (Continuous Integration and following : Testing, Automated Build, Traditional versus Automated Provisioning, Provisioning, Agile Continuous Deployment and Release Planning Monitoring) Iteration Planning Recommended Learning : Please use the following available learning references for understanding the various Engineering Practices TCS Confidential
Note : This level could Note : This role can be be mapped to Agile mapped to Agile Expert Coach/Agile or Agile Consultant Champion/Agile Champion/Agile Trainer
Should have the Should have the knowledge to link back knowledge to coach Agile values values and and train teams principles to the way of working of the team Should have the knowledge to identify impediments which are preventing the team from being truly Agile Should have the knowledge to drive continuous improvement and innovation
Should have acquired E3 proficiency
Should have the knowledge to be an Agile Consultant Consultant
Daily Standup Iteration Review Iteration Retrospective Agile Estimation Product, Release and Iteration Backlog Burndown Charts Ensuring Quality in Agile Delivering Value Requirements Management in Agile (EPIC, Theme, User Stories, Use Cases, Business Case and Product Vision etc.)
TCS Confidential
1. Agile Process Handbook( Hyperlink to https://iqmskm.ultimatix.net/km /index.php/Agile_Process_Han dbook) Refer the Practice guide section for Test Driven Development and Continuous Integration and Testing. Refer the Appendix E - More on Practices for Refactoring, Pair Programming and Collective Code Ownership 2. Continuous Delivery and DevOps – A Quick start Guide Second Edition. This book available on Safari books online is a good reference for Continuous Delivery and DevOps
Please refer the Chapter 5 Approaches, Tools and Techniques. This chapter will help you to understand Source Control, Peer Review, Automated Build and Tests, Continuous Integration, Automated Provisioning and Monitoring 3. Watch the video by Bryan Beecham on Test Driven Development, Refactoring and Pair Programming available in Safari Online. 4. Watch the relevant sections in the video by Neal Ford on Agile Engineering Practices available in Safari Online. This will help you to understand Pair Programming, TDD, Source code control, Testing, Refactoring and collective code ownership in more detail 5. Extreme Programming Explained : Embrace Change : Second Edition. This book is available on Safari books Online
TCS Confidential
A really good resource to understand Extreme Programming Values, Principles and Practices 6. Extreme Programming a Gentle Introduction (Hyperlink http://www.extremeprogrammi ng.org/) 7. XProgramming (Hyperlink http://ronjeffries.com/categorie s/xprogramming/) 8. Code quality Knowmax Site (Hyperlink https://knowmax.ultimatix.net/si tes/SoftwareCodeQualitycop/default.aspx) This knowmax site has all the useful tutorials and resources to understand code quality topics including Static code analysis. 3. Experience [Expressed as duration in months / years wrt exposure, including breadth & the depth of assignments; also beyond project experience] 3.1 Type of relevant experience [Type of assignments/ areas /outcomes the professional has worked on; total time to be spent on each function] TCS Confidential
Should have experience of having worked in a Agile project for at least six months
Should have experience in being part of Agile projects for over two years
Should have experience in being part of Agile projects for over three years
Should have at least 2 years experience coaching and training Agile projects. This is in addition to the experience required for E3 level
3.2 Beyond project development experience [Includes [1) Relevant interdepartmental activities 2) Involvement in corporate initiatives]
N/A
N/A
Should have conducted at least three Agile awareness sessions
Should have played the N/A role of Scrum Master or Product Owner for at least two years
Should be an active contributor in the TCS Agile community demonstrable through interactions in forums, Q&A, delivery support, customer presentations, presales support etc.
AND Should have played the role of a coach in at least one engagement. The engagement could be in same account or a different account
Should have implemented at least 1 improvement idea within the Agile project
4. Asset Creation [Expressed as any reusable and deployable assets created in the knowledge management system of the organization] 4.1 Process frameworks defined [Articulated as the process improvement designed OR a new process framework
TCS Confidential
N/A
N/A
N/A
N/A
N/A
N/A 4.2 Tool creation [Expressed as a system or function tool designed OR created towards improving business delivery / learning]
N/A
N/A 4.3 Reusable & deployable assets created [Expressed as reusable and deployable assets created (like those in Mighty & Knowmax]
N/A
N/A
N/A
Should have created / published at least 1 asset based on best practice from account / project related to agile execution or transformation OR Should have published at least one blog on Agile topic
Should have Should have a number created/published at of externally published least 3 assets based on whitepapers best practice from account/project related to agile execution or transformation Should have published at least three articles/blogs on Knome community Should have at least one externally published whitepaper
AND/ OR N/A No. of training material created [Expressed as the number of relevant training material created towards development of a particular body of knowledge or skill]
TCS Confidential
N/A
Should have created / published at least 1 unique training material related to agile execution or transformation
Should have created / N/A published at least 3 unique training material related to agile execution or transformation
5. Industry contribution [Expressed as the contributions made to the industry. This criteria should be measured by mechanisms for e.g.: TCS GEMS]
N/A 5.1 Recognized by Peers [Expressed as the recognition given by the peer community and should be measured by appropriate mechanism such as TCS GEMS]
N/A
N/A
Should be recognized as an expert by the TCS Agile community through various activities. Activities such as extending support to accounts transforming to Agile, Agile pre-sales support, answering queries on Knome/Knowmax, actively blogging on various Agile topics in internal and external forums etc. Should have participated or presented at TCS Agile forums such as Agile Tales, TCS Agile Cafe etc.
AND/ OR
TCS Confidential
N/A Recognized by a Parent Body [Expressed as the contribution recognized by a renowned and recognized parent body]
AND/ OR 5.1 Invited as Speakers [Expressed as recognition from an external body when it extends an invitation to the speaker to address
N/A
N/A
N/A
N/A
Should be recognized by the external Agile community through various activities. Activities such as publishing articles, whitepapers, external blogging, speaking in external forums and contributing in external conferences
N/A
N/A
N/A
N/A
As defined by Lerning Object
As defined by Lerning As defined by Lerning Object Object
II Assessment / Evaluation Methodology vis-à-vis Proficiency Level As defined by 1. Certification Lerning Object [Expressed as achievement of external programs - certifying a part of the proficiency level, Achievement of internal programs internal trainings attended]
TCS Confidential
As defined by Lerning Object
As defined by 2. Evaluation Test Lerning Object [Expressed as the assessment mechanism used to assess the individual for having achieved the said proficiency level. (for eg.,Type of tests for each proficiency should be defined-like for E0 level it can be only self assessment, for E1 it can be panel review etc)]
As defined by Lerning Object
As defined by Lerning As defined by Lerning Object Object
Version History Project Details: SDLC Unit: Delivery Excellence Group Parent Project- Delivery Excellence Group1-Parent Project Owner/GL- Name & employee No : Subramanian (30104) Amendment History: Version Defined By Approved By - Role & Group Facilitated By
Date
Version 1
Durba Biswas (191335) Delivery Excellence Group
K Subramanian (30104) Head - Delivery Excellence
Krishnaiah Kolluru (153009), Corp L&D SnehaChowdary Mothkur (534985) iEvolve TD
4-Jul-16
Version 2
Arif Kazi (128758) Delivery Excellence Group
K Subramanian (30104) Head - Delivery Excellence
Krishnaiah Kolluru (153009), Corp L&D SnehaChowdary Mothkur (534985) iEvolve TD
Version 3
Arif Kazi (128758) Delivery Excellence Group
K Subramanian (30104) Head - Delivery Excellence
Krishnaiah Kolluru (153009), Corp L&D SnehaChowdary Mothkur (534985) iEvolve TD
TCS Confidential
15-Sep-16
As defined by Lerning Object
Remarks
TCS Confidential