This is the presentation from the #lastconf 2017 enjoy and please feedback. I talk about 3 big elephants which we finally tamed...automated testing, CI and CD in a datawarehouse project
10. Test Pyramid
• Maximum tests
• Closest to code
• Fastest feedback
• Close to developer
• Cohesive Units
• Less Number
• More complex
• Happy paths
• Showcase ready tests
• Sanity feedback
11. Test Pyramid in Data Warehouse
ELT / ETL
Reports
Reconciliation
Business Rules
• Power BI
• SSRS
• Store Proc
• SSIS
• Facts
• Dimensions
12. • Facts
• Dimensions
•Store Proc
•SSIS
Test Pyramid in Data Warehouse
•Power BI
•SSRS
ELT / ETL
Reports
Reconciliation
Business Rules�
👍👍
21. From extreme left to beyond
Formalized backlog prioritization , grooming
Introduced a product owner role
UAT during the sprint
DONE!DONE! Aaaaand ….DONE!
27. Key learnings
• Follow the principles; practices will emerge,
evolve
• Address the habits not the intentions
• In the absence of defined success ,‘not failing’ is
also a ‘success’
Thankyou for coming to my talk. I must admit I am a bit overwhelmed after looking at the speaker list here. However I am also quite happy to be done with my talk during the first session of a cracking two days ahead. At least I would not have to be anxious of trying to match up some of the stars lined up for the next sessions
Any ways while I am here please indulge me and come along on a journey with me of last one year which I have spent on a very interesting gig trying to address/confront/challenge and tame the elephant. Elephant , for the purpose of this talk is mindset, organizational culture, technical practices, management approach, collaborative behavior.
Thankyou for coming to my talk. I must admit I am a bit overwhelmed after looking at the speaker list here. However I am also quite happy to be done with my talk during the first session of a cracking two days ahead. At least I would not have to be anxious of trying to match up some of the stars lined up for the next sessions. Any ways while I am here please indulge me and come along on a journey with me of last one year which I have spent on a very interesting gig trying to address/confront/challenge and tame the elephant. Elephant , for the purpose of this talk is mindset, organizational culture, technical practices, management approach, collaborative behavior.
Before I start describing the various incarnations of this elephant it is worth getting to know the beginnings of this journey
Yep Baptism by Fire. That's what I decided to do.
Any automated test suite is useless unless there is a cadence to delivery of builds, focus on integrating the builds and eventually deployments of successful and valuable build. Another incarnation of the elephant in my project was championing the process of automation for these three aspects build, integrations and deployments. This section of the story is probably the most painful and memorable. As you can imagine it was’nt left up to me to determine what a build would be , would does integration mean across the stack, how should we address data during our deployments, and to top it all I was also pushing for automated test to run against each build and each deployment across environments I was clearly out of my mind. I was also asking for collaboration across a data warehouse team.
So here I am after delivering much of the goodness like automated testing and continuous build, integration, test and deployments. Still feeling a bit disappointed. Wonder why. So here is the thing. We are building things the right way but we were still not delivering it fast enough. Why. What was stopping us. With such sound, robust , repeatable build practices I thought we should be able to deliver more frequently , get feedback and then pivot right. Well I was wrong because as much as we had bought quality to the left it obviously wasn’t enough. So I thought we have to do something. I decided to move myself further to left on the scrum wall. As I call it here beyond left. I took up the role of Scrum master. It just so happened that the scrum master was leaving the project and I was asked to take up that role. And as I did last year I said Yes again.
So here I am after delivering much of the goodness like automated testing and continuous build, integration, test and deployments. Still feeling a bit disappointed. Wonder why. So here is the thing. We are building things the right way but we were still not delivering it fast enough. Why. What was stopping us. With such sound, robust , repeatable build practices I thought we should be able to deliver more frequently , get feedback and then pivot right. Well I was wrong because as much as we had bought quality to the left it obviously wasn’t enough. So I thought we have to do something. I decided to move myself further to left on the scrum wall. As I call it here beyond left. I took up the role of Scrum master. It just so happened that the scrum master was leaving the project and I was asked to take up that role. And as I did last year I said Yes again.
Any automated test suite is useless unless there is a cadence to delivery of builds, focus on integrating the builds and eventually deployments of successful and valuable build. Another incarnation of the elephant in my project was championing the process of automation for these three aspects build, integrations and deployments. This section of the story is probably the most painful and memorable. As you can imagine it was’n’t left up to me to determine what a build would be , would does integration mean across the stack, how should we address data during our deployments, and to top it all I was also pushing for automated test to run against each build and each deployment across environments I was clearly out of my mind. I was also asking for collaboration across a data warehouse team.
