The document describes the SICER framework for guiding agile transformations. SICER stands for solidarity, integrity, commitment, excellence, and respect. It provides guidelines for the necessary processes and changes required when adopting agile methodologies. The framework aims to make transformations successful with minimum costs. It emphasizes values like employee motivation, feedback, and transparency. The document outlines various phases, meetings, and documents involved in the SICER process.

1. Draft Ver 7.0
By Satish Narni

2. Why SICER ?
In Agile for doing transformation, we have Many popular Methodologies ? Like SCRUM ,Kanban,XP,Lean,..
Every Methodology talks about Certain Specific area ,But it wont talk about the changes which we need to make parallel in
the organization if we are implementing a particular methodology, And also we don’t have any particular time tested
guidelines which we can use for Transformation So here comes the SICER,
So What Is SICER ?
SICER is a Agile Framework ,which Guides all the necessary Processes required for Transformation for Software
Organizations.
SICER stands for
S = Solidarity
I= Integrity
C= Commitment
E= Excellence
R=Respect
Based on the above Core values of SICER ,We use the Agile Manifesto according to our Commitments, SICER is
a Framework which Prepares ,Establishes and Make Matured Processes for making an agile Transformation successful by
making all the required changes happen in a minimum cost to Organization ,Means All Startup's and Medium sized
Companies can now reap the fruits of Agile through SICER .

3. Based On the Core Values Of SICER , We follow the Agile Manifesto
Solidarity
We Bind Together As One Team
Integrity
We Do The Right Thing
Commitment
We Keep Our Word
Excellence
We Give Our Best
Respect
We Value Each Other
In The SICER Framework,
Employee Motivation, Employee Feedback, and Transparency are the Secret Recipe’s of the
Organizations Success.

4. Agile SICER Framework is a Silver Bullet for Agile Transformation
I wish this is True - but it isn't. You can fail just as spectacularly on an Agile transformation project if we don’t follow the
principles. But here You'll fail faster as you will be using Agile (due to the transparency and visibility it brings) but
unfortunately it's not a silver bullet or an excuse to stop thinking.
Myth & Fact Of SICER

5. 1. UNDERSTAND AGILE SICER METHODS AND THEIR BENEFITS.
3. BELIEVE IN THE CHANGE.
4. FUND FOR EXPERIMENTING.
5. EMPOWER THE PROCESS AND BUSSINESS LEADER'S.
6. ACTIVELY PARTICIPATE IN DEVELOPMENT.
7. ENCOURAGE TECH AWARENESS OF BUSINESS DOMAIN EXPERTS.
8. GEAR UP TO TAKE IN MORE FROM THE TECH TEAMS.
9. REWARD SUCCESS BUT DON'T PENALIZE INITIAL SETBACKS.
10. COMMUNICATE AND FOSTER ADOPTION WITHIN BUSINESS TEAMS.
11. DEMAND FASTER VALUE DEMONSTRATION !
Things Which BUSINESS LEADERSHIP Should Do To HELP The Company To
Successfully Travel The AGILE Transformation.
2. CREATE AN AGILE GOVERNANCE BODY.

6. Consider creating an Agile GB to enhance and scale capabilities in applying Agile processes and
practices to deliver business value when strategic objectives or critical capabilities in an enterprise
require ongoing focus and specialty skills. Growing an Agile GB from scratch cannot happen overnight.
The following steps can initiate the Agile GB:
Gain support at the right level with a focus on delivering value
Identify people for leadership and other key roles that are passionate about deepening their skills and
delivering results using them
Document and share skills and methods; get training and mentoring where skills fall short
Apply the skills in pilot projects that are important to the enterprise while mentoring others to expand
the capabilities
Put in place output measures that track results delivered
Formalize the team, integrate it with strategic planning, and expand it across the organization
Continue to improve, adapt, and advance capabilities
Importance of
AGILE GB
All the Agile GB Activities should be defined in a SICER Process Guide.

7. SICER
Process
Guide
Appraisals
Meetings
Culture
Documents
Conflicts
Resolution
Recruitment
Practices
Continuous
Leadership
Learning
Roles
SICER Process
Guide
Process
Leader
Every Organization
has its own Way of doing things So, One set of
Transformation Rules may not apply to Other
Organizations ,Because of this each organization
has to define their Processes until their process gets
matured by reducing Waste.
So, First we need to keep a Agile governing body
and it should consist of members of different
departments of an organization and they should plan
for Road Map by constantly updating in the SICER
Process Guide.

8. Most Important Waste is
Intellectual Waste
Some of the reasons for Intellectual Waste :-
1. Employees know that knowledge is power.
2. Sharing knowledge wont be rewarded.
3. Employees cannot evaluate their knowledge.
4. The opinions of non college graduates are
ignored.
5. People don't know each other enough to build
relations to trust each other.

9. Other Waste’s in
Software

10. Other Organizational
Waste’s

11. 1. The Team Size Should Be Small So that the Team Members can be more Collaborative and Manageable.
2. The Team Commitment Period should be Short.
3. The Team Should Use Automation Tools for Testing , Not Only this We should use Tools Where ever it reduces
Time.
4. The Team Should use TFS or other related software for Continuous Integration.
5. In the Commit Phase the Team Should get their Commitments Acceptance Criteria from the Testers first.
6. There should be Work In Progress Limit ,And this Limit Should Be decided by the Team.
7. Activities should be done by Pair Programming when ever its Necessary.
8. We have to first go to a customer and collect the Minimum Viable Product and also we have to find out the Pain
Points ,How they want it to be Addressed and in what Time Period, and based on the info
gathered we need to keep frequent Thought Meetings regularly with continuous customer interaction.
9. We have to give more importance to Actionable Working Hours for Planning and Estimation.
10. We wont have any minimum or maximum time limit for the meetings.
11. If they are Multiple Teams Working on one Product Backlog then we need to form a Integration Team Of
Business Owner, Process Owner and Technical leader for Resolving Interdependencies and Other
Impediments , And For this they need to Keep a Feedback Meeting for discussing about them.
How we do Things in SICER for Reducing Waste

12. Another Way Of reducing Waste in SICER
Another way of reducing Waste is to use Value Stream Mapping ,
If this technique it self takes more time means use Flow Charts and Draw the entire Process Flow
Now Test And allocate the actual time in each and every step ,Now go through the entire process
and Find and analyze why its taking that much time, Now try to reduce it.

13. Continuous Learning in SICER
In the SICER Framework,
1.The Continuous learning should be done through emails, Means instead of spending separate time
on learning activities .Daily few mails will be sent to all the employees about Leadership ,
Integrity , Compliance . We repeat the same process daily These emails contain Cut Short Information
which employees can use as Information Radiators for Continuous Improvement in a Cost Effective
Manner.
2.The Continuous learning should be done through Continuous Learning by go throughing free
Courses in a Cost Effective Manner.

14. Sno Course Name Need Of this Course Where We can Take this Course Level
Hours Needed
1
Achieve More in Less Time Using SMART Goals
Use a proven goal setting approach to increase your productivity,
leadership and management skills. Achieve more today.
www.udemy.com Beginner
1 Hours
2
Internal Communication Methods - Strategy
and Tactics
A guide to Internal Communication methods, tactics & channels & when
and how to use them to maximum advantage.
www.udemy.com Beginner
2 Hours
3
How to use positive thinking to be more
successful. DEMO
Learn how to get what you want out of life by thinking with a positive
manner.
www.udemy.com Beginner
1 Hours
4
How to overcome fears How to heal and remove common fears www.udemy.com Beginner
2 Hours
5
The Art of Developing Self-Awareness
A step-by-step guide to greater happiness, success & self-esteem by
activating positive change from the inside out.
www.udemy.com Beginner
1 Hour
6
Improve your world and life with Hypnosis
Change your perception of the world to having your glass half full with
natures gift hypnosis for more happiness in life
www.udemy.com Beginner
1 Hours
7
Culture | How to Support Team Culture
Understand how to create an atmosphere that has a sense of team for a
diverse group of people
www.udemy.com Beginner
1 Hour
8
The Power Of Questions
Questions can flip your life around real easy? Empower your life NOW by
always asking the right questions.
www.udemy.com Beginner
2 Hours
9
Professional Communication Essentials
Fundamentals of communicating in the workplace, including effective
email and letter-writing techniques, and web search.
www.udemy.com Beginner
1 Hours
10
How To Double Your Productivity By Tomorrow
Morning
12 counter-intuitive steps to double your productivity by tomorrow
morning and master time management
www.udemy.com Beginner
2 Hours
Details Of Free Courses

15. IDENTIFYING ORGANIZATIONAL CHANGE
For Bringing an Agile Transformation Every organization has to Look into the Below Mentioned things
with Out Fail
VISION+SKILLS+INCENTIVES+RESOURCES+ACTION PLAN
Then ORGANIZATIONAL Change Happens With Out Fail, Other wise It brings Below Chaos in the
Organization.
Vision Skills Incentives Resources Action Plan Change Good Indicator
Vision Skills Incentives Resources Action Plan Confusion Bad Indicator
Vision Skills Incentives Resources Action Plan Anxiety Bad Indicator
Vision Skills Incentives Resources Action Plan Resistance Bad Indicator
Vision Skills Incentives Resources Action Plan Frustration Bad Indicator
Vision Skills Incentives Resources Action Plan False Starts Bad Indicator
IDENTIFYING ORGANIZATIONAL CHANGE
And If in Case If we Find Multiple Things are Missing and if we don’t fix them ,Means it will Bring a Chaos
in the Organization.

16. Fixed Mindset Vs. Agile Mindset
An Agile Mind-set
Ability to Grow
Goal is to Learn
Embrace Challenge
Failure provides Learning Opportunity
Effort is for Path of Mastery
Reaction to Challenge is Resilience
An Fixed Mind-set
Ability-Fixed, like Height
Goal-Look good
Challenge-Avoid
Failure-Defines a person’s identity
Effort-For people without talent
Reaction to Challenge-Helplessness
Agile Mind-set is the differentiator between ‘Doing’ Agile and ‘Being’ Agile

17. AGILE MINDSET ENABLERS
Demonstrate Culture Change At The ‘Top’
•Be Transparent
•Don’t treat People as ‘resources’
•Practice ‘Servant Leadership’
Redefine Success Criteria
•Focus on Delivery of Value
•Ask for the ‘Right’ information
•Bring Accountability at Team level
Encourage Continuous Improvement
•Enable Fast and Regular Feedback
•Spur Positive Disruptions
•Celebrate Successes
Make Changes at Org. Level
•Modify Appraisal Process
•Have People Friendly Policies
•Align the entire Organization
Address Middle Management Insecurities &
Concerns
•Help bring out in open
•Help them to visualize the benefits of their new
role
•Pair with Transformed Managers

18. AGILE MINDSET INDICATORS
1. Teams look at Failure as Learning Opportunity.
2. People Are ‘Intrinsically’ Motivated.
3. Teams welcome Diversity of Thought.
4. People Are having Fun At Work.
5. Teams Are Working at Sustainable Pace.
6. Teams are ready to Embrace Change.
7. Teams Practice ‘Brutal’ Transparency.
8. People have Urge to Communicate & Collaborate.
9. People Willingly Share Knowledge.
10.Teams Themselves Observe Anti Patterns

19. In the SICER Framework, We Will be having
1.Team Info & Assessment Document
2.Commitments Document
3.Commitments Work Break Down Document
4.Commitments Progress Document
5.Commitments Impediments Document
6.Commitments Technical Issues & Architecture Document
7.Commitments Review Document
8.Maturity Feedback Document
9.SICER Process Conflict Form
10.Commitments Appraisals Form
11.SICER Meeting Minutes Form
All the SICER Framework Activities SHOULD be defined in a SICER Process Guide.
Documents in SICER

20. In Agile we hear this jargon "CROSS FUNCTIONAL TEAM" lot of times so By the way what is a cross functional
team !!! In Agile SICER Framework every event and task is exactly time boxed. Because of this a team formed for working In a
traditional waterfall model may not achieve their goals because of their Team Structure.so for this we use the concept of a cross
functional team . So what is it exactly ?
This is a Single Super Team where different teams of developers ,testers , business analysts and others form like a single team
and collaborate each other effectively by sharing their views and by helping each other in achieving the sprint goals starting
from requirements gathering to the time its deployed .So does this mean that if you club different teams into one team then we
can call that team as a cross functional team. Theoretically yes , but for the successful execution of the project in the Agile
SICER Framework the team members should posses some basic qualities and necessary technical knowledge. Then only the
project will be successful otherwise though if we follow the SICER Framework rules then also it will fail and then at end as a last
resort we use a Fish Bone diagram for finding the root cause of the failure.
So every team member should posses these below basic qualities
1.He or she should have required technical knowledge and show enthusiasm to learn new technologies when necessary.
2.He or she should know and use only One common language for communicating among the other team members is
necessary.
3.He or she should be collaborative and help others.
4.He or she should be self motivated ,organized , transparent and disciplined.
And if the cross functional team posses these qualities then we can say that we formed a cross functional team with assured
success of the project.
Self Organized Dedicated-Cross Functional Team in SICER

21. The Success Mantra For Hiring a Agile Team is that the HR Team have to follow few
things means they have to keep few tests for the Team members for checking whether He / She really have the Agile
Attitude which is the key for the overall success of the Project.
So what is “Agile Attitude” In General Terms It means He / She have to be
“ A Part of owning the Rapid Changes and in doing so they have to be
Adaptable to the Situations aroused with a Positive Outlook in a Disciplined , Collaborative and
Transparent Perception by Showing Respect to Others. ”
The Agile Coach with the Help of the Hiring Team have to check these Qualities while Selecting the Team Members .So
How do we need to check these qualities:-
1.Group Discussion:-
Keep a Group Discussion In this discussion see how they are communicating in a Team and also check whether they are
showing Positive Outlook in that discussion .
2.Team Task:-
Organize a Team Task and in this task check whether they are taking initiatives according to the changing plans or not and
also check how they are coordinating with the other Team members in achieving the team goal.
So by these tests we can find whether a team member has the Agile Attitude or Not.
3.System Test:-
Keep a System Test on the area which they are needed.
Success Mantra For Hiring a Agile Team in SICER

22. In the Decide Phase we keep Thought Meetings and then we keep Team Assessment Meeting to decide
the Team Members which should be a Dedicated Cross Functional Team.
First ,In the Commitment Phase we Keep Business Clarity meeting to analyze the Enhancements
and in the Commitment Meeting the team will Freeze the requirements ,In this Meeting the Team will Give
the Work Breakdown Structures for all the requirements in a Project .
Secondly , In this Phase we use meetings Like Commitment Progress Meeting
and Business Clarity Meeting for resolving Business related doubts of Developers and Testers after this
according to our needs we Keep a Future Release Commitment Planning Meeting.
In the Explore Phase we do Commitment Review Meeting for taking Approval on the developed s/w
and also at the end we keep a Maturity Feedback Meeting
for making these 3 Phases Matured.
1.Decide Phase
2.Commit Phase
3.Explore Phase
Phases in SICER

23. Commitment
Review Meeting
Maturity
Feedback
Meeting
Commitment
Progress Meeting
Business Clarity
Meeting
Team Assessment
Meeting
Test Driven
Development
Commitment
Meeting
Thought Meeting
Business Clarity
Meeting
Decide Commit Explore
Future Release
Commitment
Planning Meeting
Process Flow in SICER

24. Meetings in SICER
In SICER Framework We wont have any minimum or maximum time limit for the meetings.
1.Thought Meeting :- In this meeting team analyze and share their thoughts among the team members, And
In this meeting any one can Participate according to the need.
2.Team Assessment Meeting :- In this meeting Technical Manager ,Business Owner ,Process Owner and
Team Manager will decide what Assement should be kept to decide the team.
3.Business Clarity Meeting :- In this Meeting Business Leader will clarify about the commitments to the
team members, And In this meeting all roles except Team Manager remaining all should be present.
4.Commitment Meeting :- In this Meeting Team play a Planning Poker Game and give estimation through
work breakdown structure , And In this meeting Process Owner ,Technical Manager and Team should be
present.
5. Commitment Progress Meeting :- In this Meeting Team will discuss about what they have done
yesterday what they are going to do this day and they need to talk about the impediments if any , And In this
meeting Process Owner ,Technical Manager and Team should be present

25. 6.Future Release Commitment Planning Meeting :- In this Meeting Team
will discuss about the future Commitments, And In this meeting all roles except
Team Manager remaining all should be present.
7.Commitment Review meeting :- In this Meeting team give demo to the
Business owner, And In this meeting all roles except Team Manager remaining
all should be present.
8.Commitment Feedback Meeting :- In this Meeting team along with
Business owner ,Process Owner , Team Manager and Technical Manager sit
along with the team to discuss about the Process Maturity.
Meetings in SICER

26. How To Create Roles & Responsibilities In
SICER

27. Team
Manager
Business
Owner
Process
Owner
Technical
Manager
Team
Member
Team
Member
Take Cares
Process Maturity
Take Cares All
Managerial Activities
Acts Like a
Organizational
Stakeholder
Take Care All
Technical Work
Dedicated
Cross Functional
Execution Team
Roles & Responsibilities In SICER
Team
Member

28. Who can become a Business Owner ?
Business Owner is a part of the team and should hence be available as
much as possible to the team [close to 100%]. Hence, BO can only be
someone who is available to the team 100% of the time.
Business Owner needs to understand the big picture – the
philosophical as well as practical aspects of what is being built.
This would often require excellent domain knowledge.
Business Owner should know what will work – hence, exposure to
marketing and sales is important. This is also often called Voice
of the Customer. Basically, Business Owner should deeply
empathize with customers – their needs, their frustrations and
their wishes.
Availability
Domain Knowledge
Voice Of Customer
Agile Knowledge
He Should have Agile Knowledge.

29. Who can become a Process Owner?
Servant Leader
He Should act like a Servant Leader and Facilitate TM in All the
People Management Activities and resolve all the Impediments, the Primary responsibility
of the PO is to make the Process matured by reducing Waste.
Process Owner is a part of the team and should be always
available to the team [100%].
Availability

30. Who can become a Team Manager?
Team Manager should know Management 3.0 techniques.
Technology HR Specialist
Every Team Manager is a part of the team and so they should be always
available to the team [100%].
Availability
Agile Knowledge
Team Manager Should have Agile Knowledge.

31. Who can become a Technical Manager?
Technical Manager should know technology – programming and
they should actively involve in the Architecture and other
Technical Issues.
Technology Specialist
Every Technical Manager is a part of the team and so they should
be always available to the team [100%].
Availability
Technical Manager needs to understand the big picture – the
philosophical as well as practical aspects of what is being built.
Domain Knowledge
Agile Knowledge
Technical Manager Should have Agile Knowledge.

32. Who can become a Team Member?
Team Member should know both technology – programming, UI,
QA is required .
Technology Specialist
Every Team Member is a part of the team and so they should be always
available to the team [100%].
Availability
Team Member needs to understand the big picture – the
philosophical as well as practical aspects of what is being built.
Domain Knowledge
Agile Knowledge
Team Member Should have Agile Knowledge.

33. The SICER Framework,
The Employee Appraisals are done by the Employees Themselves in the Form of 360 Degrees Feedbacks.
The Process Owner along with Business Owner and Technical Manager Observes the Fairness of the execution
of the 360 Degrees Feedbacks.
In this Process The Technical Manager Checks the Individual Technical Learning Skills
Business Owner Checks the Project Goals Of the Team has been Achieved Or Not
Process Owner Checks the Integrity , Compliance and Cultural Space.
Appraisal Process in SICER

34. Culture in its purest form is Morals and Values .
So, Culture is simply How we do things in a Ethical Manner which is acceptable by Every One.
Then How is Culture linked to Agile SICER Framework Transformation of an Organization ?
Is it a new kind of Revolution which is taking Place in the 21st Century.
Yes ,As Agile SICER Philosophy is Completely Based on the True Morals & Values of Life like
Honesty,Cooperation,Motivation, and Freedom. So, In Simple Terms Agile SICER Philosophy Is all about
" Achieving a Organizational Goal by Showing and Practicing the Highest Values of Life through
Team Cooperation in a Transparent Manner ".
So Which Should Happen First.
Agile SICER Framework Transformation or Cultural Transformation ?
This Transformation should start with By Building Rich Cultural Values in the Teams and then we should
start applying the SICER Framework across the Organization.
Finally What Agile SICER Framework Says is
“An Agile SICER Framework Transformation Can’t happen Completely Without a Cultural Transformation
and a Cultural Transformation can’t happen in a Day or So, As it should take place smoothly in
a Slow and Continuous Learning Manner through Continuous Improvement” .
Culture in SICER

35. In the SICER Framework,
The Conflict is Not treated as a Problem with Two Or More Individuals ,
But its Treated as a Outcome Of Un Matured Process.
So , If Employees Have any Conflict then we have to First Talk to Process Owner
to keep a Process Maturity Review Meeting with Reporting Managers and the Process Owners
and in front of them they have to Fill a Process Conflict Form,
Then in the Next meeting we have to find a Solution for Making this Flaw in the Process Resolved
So, That the Process Becomes Matured.
Conflict Resolution in SICER