Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Crystal
1. Crystal A Remedy for Prescriptive Agile Abid Quereshi [email_address]
2.
3.
4.
5.
6.
7.
8. The Crystal Family A Specific Family of Self-Adapting Methodologies with a common structure (or DNA) Related by adherence to common philosophy and principles
9.
10.
11. Strategic, Economic, Co-operative Co-operative Game Resource constrained series of activities involving Invention and Communication Goals are to deliver software in this game and to set up for the next
15. Safety in a Scrum Sprint Priorities Quality Team size & Resources Fixed Time Safe Zone iterations
16. Safety in a Project using Scrum Priorities Quality Team size & Resources Fixed Scope Safe Zone
17. Project Safety Crystal and Fixed-scope Fixed-Time Quality Team size & Resources Fixed Time Fixed Scope Safe Zone
18. Efficiency Efficiency Cross Functional Teams More Continuous Integration Robust Definition of Done More Frequent Releases High Resolution User Cases Quality Team size & Resources Fixed Time Fixed Scope Integration Tests Automated Acceptance Tests Value stream mapping Feature prioritization
19. Priorities Efficiency Cross Functional Teams More Continuous Integration Robust Definition of Done More Frequent Releases High Resolution User Cases Quality Team size & Resources Fixed Time Fixed Scope Integration Tests Automated Acceptance Tests Value stream mapping Feature prioritization Check-in Dance Code Reviews Config Management Fixed amount of WIP Change Management Reusable Templates BDD TDD Daily Stand-up
26. Why Properties ? Properties Do you have ..? (properties and outcomes) rather than Do you do .. ? (processes and methods) Properties can be measures qualitatively and quantitatively
27. Properties Process viewpoint Measurable Outcomes or Properties viewpoint We are doing 3 week sprints We deliver software to the user every 3 weeks We hold retrospectives at the end of every iteration We’ve implemented 2 processes removed 1 process, and tried 1 new technique We have daily stand-ups We’ve had 4 breakdowns in communication and 3 impediments removed We have a grievance procedure We’ve had 0 turnover in the past year Requirements can not be added once the sprint has started Team member has 3 interruption per day on average We hold planning meetings at the start of an iteration It takes me 3 days to get an answer to a user oriented question We do continuous integration How many regression bugs were introduced during the last sprint
28.
29.
30.
31.
32. The Crystal Family Safe Zone Cross Functional Teams More Continuous Integration Robust Definition of Done More Frequent Releases High Resolution User Cases Quality Team size & Resources Fixed Time Fixed Scope Integration Tests Automated Acceptance Tests Document templates
38. Crystal Clear in the Crystal Spectrum 6 people (3 to 8) 20 people 40 people 80 people Clear Yellow Orange Red more people Darker Colour Team Size
39. Crystal Clear in the Crystal Spectrum C Loss of Comfort (awe.. shucks) D Loss of Discretionary Money, (e.g. system errors have manual fix) E Loss of Essential Money. (e.g. system errors cause bankruptcy) L Loss of Life
40. Crystal Clear in the Crystal Spectrum L 6 E6 D6 C6 L 20 E 20 D 20 C 20 L 40 E 40 D 40 C 40 L 80 E 80 D 80 C 80 Clear Yellow Orange Red Criticality Team Size
41.
42. Dedicated Team Roles Expert User Lead Designer Executive Sponsor The rest Designer Programmer
43.
44. Processes must evolve to improved Efficiency and Habitability Reflection is a vital part of building experience Processes should be nested in natural cycles and accompanied with refelction Processes
45.
46.
47. Processes Project Delivery Iteration Day Integration Episode Charter Plan Plan Standup Design & Check-in Design & Check-in Build and test Design & Check-in Design & Check-in Build and test Standup … . …. …. …. Plan Deliver Plan Reflect
48.
49.
50.
51.
52.
53.
54.
55.
Notes de l'éditeur
Crystal Clear title was a mistake.
Solutions must be at least as varied and variable as the problems they are trying to solve
Meta framework or meta methodology Main foundation or basis – Co-operative game
Scrum uses this analogy –
You plan and map Plan changes once you see the terrain
Habitability may run against efficiency but they often converge in the end. Upfront modelling to avoid recoding, refactoring Enough code to discover a model worth documenting You will know when you reach the point of diminishing return.
Unrealistic for many projects Scrum treats a project as a black box with complexity ready to be discovered Question How many practice scrum How many deal work with projects that have Fixed-Deadlines, Fixed-Scope, Both, Scrum
Team enforces
Business accepts empirical nature of Scrum Business accepts impossibility of fixed-scope within a fixed-price and fixed-date
Scrum is the art of what is possible How can you make this possible? Through efficiency – minimizing waste
Efficiency is a 5 th variable Deficient or Barely Sufficient – for project safety Processes, Strategies and Techniques The point of too much process, too many strategies and techniques
Efficiency is a 5 th variable Deficient or Barely Sufficient – for project safety The point of too much process
The point of too much process Sensitive to the point of diminishing returns
Lighter methodologies are better until they run out of steam The sweet spot
Habitability may run against efficiency but they often converge in the end. Upfront modelling to avoid recoding, refactoring Enough code to discover a model worth documenting You will know when you reach the point of diminishing return.
Not in priority Grouped to Primary and
Properties can be measured. Properties are the point Use properties as a ubiquitous language
Increased frequency of delivery - how often – versus “We are doing three week sprints” How many new practices have we added or old practices removed - versus – “Are we holding retrospective meetings (process)” How long does it take for me to get a question answered by someone on my team? – versus – “Are we doing have daily standup” How much turnover? How many interruptions per day? How long does it take for me to get a definitive answer to a user-oriented question? How many bugs per.. How much time between when the bug is created and when it is reported?
Think of strategies
Think of techniques
Techniques Work product examples Strategies
Establish a lead to avoid the “wrong” type of conflict. Necessary to outline responsibility and accountability
![Crystal A Remedy for Prescriptive Agile Abid Quereshi [email_address]](https://image.slidesharecdn.com/crystal-100226090507-phpapp01/85/Crystal-1-320.jpg)
![What other have said ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)