This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Most scrum masters don’t take these points into consideration while planning their sprints. Usually, scrum masters don’t take this into consideration while planning their sprints. Again, scrum masters don’t take this into consideration while planning their scrums. new bugs can occur at any point in time.
Most scrum teams don’t take these points into consideration while planning their sprints. Usually, scrum masters don’t take this into consideration while planning their sprints. Again, scrum masters don’t take this into consideration while planning their scrums. Let’s dive in straight away.
Most scrum teams don’t take these points into consideration while planning their sprints. Usually, scrum masters don’t take this into consideration while planning their sprints. Again, scrum masters don’t take this into consideration while planning their scrums. Let’s dive in straight away.
Experience in ContinuousIntegration. Agile Methodologies: Scrum ( Jira ). Work with TDD & CI. Spanish native or bilingual. 2+ years of backend development experience. Experience with some of the following languages: PHP, Kotlin, Node.js. Experience working with Docker. DevOps experience. Strong knowledge of SOLID.
Christian is a former practitioner of Agile methodologies, particularly eXtreme programming, with experience in practices like TDD, continuousintegration, building pipelines, and evolutionary design. Learn more about this workshop here. Learn more about this workshop here. and optimization consulting.
You will have to write code and therefore we will force you to do TDD. You will also learn ContinuousIntegration. Knowledge of Agile Methodologies (SCRUM). To know how to work with CI & TDD. You will be applying best practices in software development. You will learn how to do refactoring to a DDD architecture.
He is a former practitioner of Agile methodologies, particularly extreme programming, with experience in practices like TDD, continuousintegration, build pipelines, and evolutionary design. Dave Farley – Co-author of the Jolt-award winning book Continuous Delivery.
Having had different roles as software developer, software architect, project manager, Scrum Master, Product Owner, coach&trainer and head of software development he can rely on plenty of experience in a variety of settings and industries. Also, he is a co-author of the book “Software Architecture Metrics” book.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content