Kicking off agile remote teams

So your project is just getting started. Or maybe you're just about to embark on a new release. Or new members just joined the team. What now?

In either situation, your project will have a lot of energy and attention right now. But at the same time, there's probably a lot of uncertainty about what to do first. Many projects waste this valuable time without a clear plan or purpose. In Exilesoft, we have refined activities to deal with these problems, even with the additional constraint that the team may be distributed geographically.

In this workshop, we share a typical plan of what activities to do every day in the first weeks together with a set of activities which yeld tangible results in terms of team building, vision, architecture and a coherent working system in a minimum of time. Participants will get a chance to practice the skills as well with several interactive exercises.

 
8 favorite thumb_down thumb_up 5 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. Meetings you need when starting your agile project
  2. Interactive simulation exercise of a startup meeting
  3. How to follow up on your projects once started
  4. Interactive simulation exercise of a remote demo

Learning Outcome

  1. Thushara and I are individual presenters presenting in various conferences. At work, she heads the project office while I work as the chief Scientist of Exilesoft. When we initiate a project, we both get together and lay the foundation for a successful project engagement.
    Lesson 1 : PMO and technical integration in agile project initiation.
  2. Its important to understand the objectives and expectations from customer management stakeholders as well as from offshore vendor management stakeholders
    Lesson 2: How to facilitate such workshop with senior executives including CXOs.
  3. It’s a common belief that it’s hard to get the senior management understanding and buy-in for the agile project execution model.
    Lesson 3 : How do we facilitate the customer management and the offshore vendor management to get in to such understanding.
  4. Unfortunately many agilists don’t believe that they can deliver software within the first 2 weeks of the projects. We do that in our projects.
    Lesson 4 : How to lay the foundation to deliver software within the first 2 weeks.
  5. Yes! We do agile, still we got to make sure that information is transparent to all project sponsors and other stakeholders throughout the project.
    Lesson 5: enabling the project transparency
  6. Customer may not an expert to work with remote teams.
    Lesson 6 : How we prepare the customer stakeholders to face the challenges in remote team development.
  7. How do we wrap up such agile project initiation workshop?
    Lesson 7 : defining the outcome and issuing team charter of the agile project engagement.

Target Audience

Team members on remote development teams

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Meghan Robinson
    By Meghan Robinson  ~  1 year ago
    reply Reply

    Hi Johannes, 

    I’m intrigued by your scrum and agile expertise! I’m wondering if you would be willing to write a piece or give us permission to highlight an existing article on the new AgileCareers Blog. AgileCareers is powered by Scrum Alliance and is the only job board dedicated to connecting Scrum and Agile organizations with qualified, passionate Agile professionals.

    Click below to view the blog: http://membership.scrumalliance.org/blogpost/1322603/AgileCareers-News

    If you wish to discuss further, please email me at mrobinson@scrumalliance.org. I look forward to hearing from you!

     

    Thanks,

    Meghan

  • Ravi Kumar
    By Ravi Kumar  ~  4 years ago
    reply Reply

    Hi Johannes,

     

    Thanks for submitting your proposal.

     

    Given the special requirements that your've mentioned and the level of maturity of the audience I doubt if the session is viable and render value for the time of 90 min. Is there a way you can convert this into a 20 min experience report. I see this as a potential talk only if there are some unique activities that you do which could be a great learning for the audience attending the session.

     

    Best regards,

     

    Ravi

     

    Best regards,

     

    Ravi

     

    • Johannes Brodwall
      By Johannes Brodwall  ~  3 years ago
      reply Reply

      Hi Ravi. Thanks for your comment. In 90 minutes, we can cover the outline of the kickoff process as well as run the audience through several exercises. We can change it to a 20 minutes experience report, but then we will lose the participation aspect of the workshop.

  • Raja Bavani
    By Raja Bavani  ~  4 years ago
    reply Reply

    Dear Johannes,

    Please add details on how (and in how many projects / over how many years) you implemented the set of activities of recommendations.   That will help us understand if this is practiced and improved over time.  Do you have a written article or blogpost of slidedeck? Please share. These will help our reviwers and program committee.

    Regards,

    Raja

     

    • Johannes Brodwall
      By Johannes Brodwall  ~  3 years ago
      reply Reply

      Thanks for your comment, Raja. Thushara and I have implemented these practices for about a year for customers in the Scandivian and Australian market. The lessons are drawn together from several presentations, so we don't have a representative slide deck at this time.


  • Liked Ravi Kumar
    keyboard_arrow_down

    Ravi Kumar - Evolutionary Approach for Maturing Agile Adoption in IT Services

    Ravi Kumar
    Ravi Kumar
    Agile Coach
    AgileFAQs Tech
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Change is a necessity and fact of organization sustenance and survival. Some changes are quite disruptive while others evolve gradually. Agile when compared to the many of the other models is radical and requires some fundamental shifts both in culture and traditional management practices. The Indian IT Services industry is at the crossroads of change with a heavy influx of agile projects in the recent past. Effective change in the context of agile with a heavy baggage from the past makes it harder. Business still has to continue and projects must be executed; so how do we go about an effective agile adoption/transition.

    This talk will try and look into the complexity and inhibitors of successful agile adoption in a typical large IT Services organization and questions the viability of certain agile methods such as Scrum and XP. We will explore why evolutionary methods such as Lean/Kanban are better fit and the necessity for evolutionary software development such as emergent design as a core premise for delivering Professional Software Development Services. Finally we also challenge the current status quo that is detrimental to a meaningful agile adoption and suggest few positive changes with Agile IT Services Manifesto.

  • Liked Giovanni Asproni
    keyboard_arrow_down

    Giovanni Asproni - Methodology Patterns: a Different Approach to Create a Methodology for Your Project

    Giovanni Asproni
    Giovanni Asproni
    Consultant
    Asprotunity Limited
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Advanced

    In the software world we have been looking for “The Methodology” to solve our software development sorrows for quite a while. We started with Waterfall, then Spiral, Evo, RUP and, more recently with XP, Scrum, Kanban, DAD, SAFe (there are many others, but, their impact, so far, has been limited).

    In this tutorial, I'll show why this search for the holy grail is bound to fail--each methodology has strenghts and weaknesses that make it suitable only in some contexts--and I'll describe a different approach based on patterns and pattern languages, that teams can use to create their own methodologies to suit their specific needs, which, in my experience, has a higher chance of success. 

    The approach is based on the observation that all the practices used in all modern methodologies--e.g., user stories, use cases, team self organization, TDD, unit testing, acceptance testing, continuous integration, iterative and incremental development, etc.--come from the same set. Different methodologies just mix and match them differently. All those practices can (and many have already been) described as patterns whose relationships with each other form a set of pattern languages.

  • Liked Pramod Sadalage
    keyboard_arrow_down

    Pramod Sadalage - Ten Patterns of Database Refactoring

    Pramod Sadalage
    Pramod Sadalage
    Developer
    ThoughtWorks
    schedule 4 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Over the life of an application as requirements change, application usage patterns alter, load and performance changes the need to change database and database architecture is inevitable. There are patterns of these changes such as

    1. 1. Encapsulate Table with View
    2. 2. Migrate method from database
    3. 3. Replace method with views
    4. 4. Introduce Read only table
    5. 5. Split table
    6. 6. Make column non-nullable
    7. 7. Drop column
    8. 8. Add foreign key constaint
    9. 9. Merge columns
    10. 10. Replace columns

    In this talk we will discuss the above database refactoring patterns and different implementation techniques to enable blue, green deployments, allow for legacy applications to work with fast changing database and enable the teams to effectively refactor the database to fulfill the changing needs of the organization.

  • Liked Balaji.M
    keyboard_arrow_down

    Balaji.M - Visualization and Agile Practices to the Rescue of Traditional Project

    20 mins
    Experience Report
    Intermediate

    We are from Large Indian IT Services organisation where most of the projects follow traditional/waterfall ways of working and the mindset of the senior management is also used to this way of working for all project types (Application Maintenance, Minor Enhancement, Bug Fixing and L3 Analysis space), while these methods have their own shortfalls and projects suffer because of the methodology, many leaders still believe that by following tradtional process their problems would be solved. Through this experience report, we would like to share how Visualisation and Agile Practices rescued the waterfall project from depleting Customer Confidence and Quality of Service Delivery.

    The Project team of 9 members distributed at onsite and offshore was involved in maintenance / enhancement type of work for a large Investment Bank with several new features being implemented as change requests. Team’s responsibility starts from Analysis to Deployment into Production for the work comes in ad-hoc manner. The issues and challenges by project teams were

    • Longer duration to complete the change requests and ensuring an on-time delivery
    • Low Customer Satisfaction and Quality of Deliverable.
    • Proactively manage application issues despite higher experience of team.
    • Low employee morale
    • Lack of senior management participation and constant fire fighting with the customer.

    Project team focused on 3 areas

    Business/Client IT team

    • Prioritize the change requests by highest business/end user value (Input Cadence)

    • ‘Drive’ the development efforts to incrementally deliver

    Teams

    • Focused on speed in delivering change request by eliminating waste

    • Focused on enhancing knowledge sharing by Collaboration using Visualisation Boards and daily stand up meeting

    • Focus to Deliver right at First Time

    Management

    • Focus on the value stream (cycle time)

    • ‘Drive’ Continuous Improvement (Kaizen)

    • Manage impediments , making blockers visible

    Within 3 months of time after team started adopting the Visualisation and Agile practices the teams and senior management could see the improvement in the areas of 

    1. Increase in Balance Score Card scores from 4 to 6.5 and many areas scored 7.0/7.0
    2. Productivity improvement by 25%

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Johannes Brodwall - Practice agile programming with coding dojo

    90 mins
    Workshop
    Beginner

    A Coding Dojo is a fun and social way to become a better programmer. Johannes is an experienced coding coach who will guide you through a few hours of programming that will transform your understand your craft and yourself as a programmer. In the workshop you get to try out pair programming, test-driven development and continuous refactoring for yourself and you get lots of recommendations on how to improve your coding and testing. You will need to bring your own computer with a development environment of your choice. Recommended for Java, Ruby, JavaScript and C# developers.

    This is what previous participants say about the workshop:

    • What did you learn? New tools, pair programming and fun exercises; Ide tricks, programming language basics, testing tools, using tests as a reasoning tool; you can comfortably pair with strangers.
    • What surprised you? Small steps work better than planning; It's easy to get started when you pair program; Pair programming is nice
    • What do you plan to do next? Using TDD every day; Listen to partner more carefully - he may already have solved the problem.
  • 45 mins
    Demonstration
    Beginner

    Can you maintain agile engineering practices with a distributed team?

    Johannes is the Oslo based Chief Scientist for the Sri Lanka based company Exilesoft. In order to promote agile engineering practices, he uses remote pair programming to connect with teams halfway across the world.

    In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach. We will also cover the practical parts of remote pair programming, such as tools and setup.

    After seeing this talk, the audience should be able to remotely pair with members of their distributed team. They will also get a lot of tips on how to use pair programming effectively in both local and remote settings.

  • Liked Evan Leybourn
    keyboard_arrow_down

    Evan Leybourn - From Lean Startup to Agile Enterprise (beyond IT)

    45 mins
    Talk
    Beginner

    Traditional models of management and corporate governance are failing to keep up with the needs of the modern economy. Change, both technological and cultural, is occurring at faster rates than ever before. In this climate, modern enterprises will live or die on their ability to adapt. This is where Agile, and Agile Business Management, come in. Agile is change; changing how you think, changing how you work and changing the way you interact. This is important whether you are a software developer or a CEO.

    In this presentation, Evan will provide engaging and enlightening case studies of Agile beyond IT; from lean startups to large enterprises. These will be reinforced with practical approaches for the leadership of teams, divisions and businesses. 

    Taking the successful concepts and methods from the Agile movement and Evan's new book, Agile Business Management is a framework for the day-to-day management of organisations regardless of industry, size or location. We will discuss processes, techniques, and case studies for the 4 key domains from Agile Business Management;

    1. You, the Agile Manager - What makes a good manager and how do their responsibilities change?
    2. Integrated Customer Engagement - Collaboration and communication techniques to build trust and deliver Customer needs efficiently, with minimal waste, and to everyone's satisfaction.
    3. The Structure of an Agile Organisation - Efficient, transparent and collaborative techniques to manage empowered staff.
    4. Work, the Agile Way - Managing all types of business functions, from software, HR, finance to legal, by using Just-In-Time planning and Incremental or Continuous Delivery processes.

    Ultimately, the goal of this presentation is to make you think about your role as a leader. 

  • Aman King
    Aman King
    Agile Technologist
    ThoughtWorks
    schedule 4 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Are you an Agile Practitioner? Or are you responsible for Agile transformation?

    Organizations that have begun their Agile journey welcome the guidance of an experienced Agile Coach. But external guidance cannot continue indefinitely as the only way to scale Agile.

    If you are in an Agile team, are you prepared to take on the coaching role for other teams once your Agile Coach moves on?

    If you are a manager, are you looking at grooming in-house coaches to scale and self-sustain transformation?

    The transitioning of practitioners into coaches can be key to your Agile journey. Individuals get to build on their potential, while the organization becomes more self-reliant.

    This session explores my personal journey from practitioner to coach. It should help you too in taking that first jump into the role of a coach. I will share real-world examples of dealing with on-the-fly situations, and of preparing upfront where possible. I will recommend resources, and mention handy techniques that should be in a coach's toolkit. The session essentially provides a kick-start for first-time coaches.

  • Liked Vinodhini
    keyboard_arrow_down

    Vinodhini - Robotic Warehouses, Alien Domain, Offshore developers, Visionary customer : Saved by agile

    20 mins
    Experience Report
    Intermediate

    Here is a case study of how agile outsourcing can be practically applied even when the business domain is very complex and alien to offshore teams.
    The example is a project in which Exilesoft provided for a leading Norwegian producer of Robotic warehousing solutions. The project involved transforming their legacy application, produced using multiple suppliers and methods, into a newly cast application solution. This project also had its own share of typical challenges.

    • Lacked definitive and reliable documentation,
    • Domain knowledge was limited to a few very busy individuals,
    • Development and redeployment could not interrupt attention to current customers,
    • Complexity was high and design was fragmented, and
    • Focus heavily invested on current product and customer support

    These limitations along with the lack of understanding of agile methods strongly suggested the use of a method adaptive in nature, and not heavily vested in large inflexible legacy elements.
    We commenced the engagement with two pivotal elements; client awareness (agile orientation) and a roadmap of committed involvement. To lay credibility this had to be backed up with proven result delivery in the very early stages. It allowed for flexible adaption, and the creation of an atmosphere that fostered client interest.

    During this session, we will take the audience through a small video clipping of such a warehouse. We will elaborate how the customer and offshore developers worked together using agile in a highly integrated team collaboration model to achieve success within a very short time frame.

    The session will cover the following key areas:

    How such projects can be initiated

    - What type of team model and contract type we used

    - How we did the agile transformation with the customer

    - How the roles were assigned between offshore and onshore team members

    - To improve remote collaboration the tools and techniques we used

    - Techniues learned to get teams up to speed with the new domain

    - As we go along, the process changes we identified and implemented to make things work better.

    - Agile engineering practices and team dynamics that helps in such situations

  • Liked Andrea Heck
    keyboard_arrow_down

    Andrea Heck - Distributed Product Owner Team for an Agile Medical Development

    Andrea Heck
    Andrea Heck
    Agile Coach
    Siemens AG Healthcare
    schedule 4 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    We are developing medical imaging and workflow software in an agile way with development teams distributed to several countries. One of the major challenges is how to set up and communicate within the Product Owner team. There we have to deal with the distribution, e.g., have the Product Owner either onsite with her peers or with her Scrum team, travelling, or with proxy. We need people who are good in two different fields of knowledge: medical and software development. As a third issues, the environment of the customers may be different in different countries.

    We have ramped up local Product Owners in different countries, have found local collaboration customers, and have developed a set of communication channels and workshops how to synchronize Product Owners in the team, share a common vision and backlog with their Scrum teams, and collaborate with customers locally and globally.

  • Liked Prasanna Vaste
    keyboard_arrow_down

    Prasanna Vaste - Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    Business Analyst
    Thoughtworks
    schedule 4 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Tathagat Varma - Agility @ The Scale of Busine$$

    Tathagat Varma
    Tathagat Varma
    Founder
    Thought Leadership
    schedule 4 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    [24]7 Customer, Inc started out in customer service space from Bangalore in 2000. Today, it is a sucessful mid-size company in voice-based customer support that also creates IP and products in big data and predictive analytics for some of the biggest names in business, and is a a high-growth company headquartered out of US. The growth in product R&D happened both organically as well as from acquisitions across multiple geos. While the initial / startup stage processes had been extremely successful in building the company's strong foundation, it was felt that the next stage of growth might not be a linear extrapolation of the past successes. Recognizing this futuristic need, it initially embraced agile software development methods in Q1 of 2013 to improve responsiveness, predictability and time to market in the product development organization. In Q2 of 2013, it embarked upon an ambitious company-wide program. The charter was to establish an end-to-end execution framework to make the entire operations efficient and effective - right from marketing and pre-sales to delivery, deployment, operations and ongoing optimization. 

    In this session,

    • We will analyze challanges involved in scaling-up agile adoption outside the software team across the entire organization.
    • Specifically, we will also discuss how we addressed some of those unique challanges that are associated with growth and scale, and
    • What does it take to achieve true end-to-end agility. 
  • Liked Naresh Jain
    keyboard_arrow_down

    Naresh Jain - SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Johannes Brodwall - Bare-Knuckle Web Development

    Johannes Brodwall
    Johannes Brodwall
    Chief Scientist
    Exilesoft
    schedule 4 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Can you go faster with less weight?

    We have all learned the benefit of reusing application servers like JBoss, ORMs like NHibernate or dependency injection frameworks like Spring that "solve all the plumbing code for you", but how real are these benefits really? Most developers struggle using techniques like test-driven development and refactoring effectively in their day to day project. Many developers spend a majority of their day finding out which magic incantations will make your framework solve your requirement.

    Yes, frameworks probably will reduce the size of your code base. But will their reduce the time it takes to develop that code base? And perhaps even more pressingly: How certain are your estimates when you know that a the majority of your work is to find out exactly which few lines of code you need to change by debugging, reading documentation and searching for answers on stack overflow?

    When I was first learning math, my dad told me that I didn't to use a calculator before I could do the math without it. In the same tradition, this talk builds on the premise that you shouldn't use a framework that you can't do without: I will create, live, a realistic web application without generators, without frameworks and without bullshit. Instead, I will use test-driven development to ensure steady progress to a solution with no magic.

  • Liked Aruni Siriwardene
    keyboard_arrow_down

    Aruni Siriwardene - The Waterfall enthusiast and The Agile Contract

    45 mins
    Talk
    Intermediate

    A traditional software development project entails specifics around elements in or out of scope, tied up to deliverables, all ensconced within specified estimates and timelines, subjected to legal clauses for everything from acceptance to indemnities. For Agile contracts, the boundaries of legal intervention must stand; merely due to the marriage of parties when a project is executed; the definitions of boundaries must be established be it scope, budget or timeline and all standard deliverables from a traditional project stands; yet, the execution is as diverse as chalk and cheese.

    What are the key criteria to be aware of when we define Agile contracts; as in typical agile projects, should the client be involved in mutually drafting the contract? How much legal intervention can we allow? What happens to deliverables and expenses when delays occur and scope boundaries are reduced? Can blame be apportioned to an extent that each party will have to indemnify themselves?

    An Agile contract needs to reflect the nature of the engagement; no template contract with standard clauses can be coaxed upon a true agile project. In line with the Agile principles and values and targeted to the agile manifesto; Agile contracts should be just that – Agile!

  • Liked Anuradha Gajanayaka
    keyboard_arrow_down

    Anuradha Gajanayaka - Convincing Agile Estimation to a non-Agile Project board

    20 mins
    Case Study
    Intermediate

    Software development estimates are considered to be evil. If you have attended Agile India 2013 you know what I’m talking about! Both we use user stories and points or Gantt chat and hours, we have never discovered that magical formula for the right estimation.

    But is it something you dare to tell your project board?

    The bad news is that the software industry may not be able to forgone Estimate for a foreseeable future. The good news is that agile estimation techniques provides some kind of balance between need for estimates and inability to predict future.

    Still, our Agile Estimates can be really challenging when the receiving partly has no clue about Agile Software Development, specially the customers, members of project control boards and senior management.

    In this case study, I would like to draw the experience on how we used certain techniques and invented some tools to convince a non-Agile, traditional project board to use Agile Estimates.

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    Pradeepa Narayanaswamy - WORKSHOP- Defining Behaviors as a team

    45 mins
    Workshop
    Intermediate

    In lot of agile teams, often times, all the team members will be doing the grooming and planning exercise as a team. Often times, defining the behaviors is either ignored, overlooked, skimped or done by individuals on their own without a common understanding as a team.

    To solve this problem, I have used this hands-on time-boxed activity for all of my teams to define behaviors as they move along in the sprint. This will help all the team members to have a shared understanding on their users and their behaviors as it relates to their user story. This is an activity that any agile team member can take and implement the next day at work.

     

     

  • Liked Anuradha Gajanayaka
    keyboard_arrow_down

    Anuradha Gajanayaka - Some say they do Scrum to be agile ...

    45 mins
    Experience Report
    Intermediate

    In the challenging context of offshore Agile Software Development, not everything in the book would work. In this experience report, I would like to discuss how the teams can tailor the current so called standard Agile methodologies/practices (within the guidelines of the Agile Manifesto), yet become successful in deliveries.

    In the session, I would like to discuss some of the agile practices the audience is using and then discuss the challenges they face when it comes to Agile Offshore Development. Then I would like to draw my experience on offshore software development projects where we successfully used Agile concepts and demonstrate how to customize those standard methodologies/practices within the Agile Manifesto Framework.

  • Liked Shashank Teotia
    keyboard_arrow_down

    Shashank Teotia - TDD and CI - closing the agile loop over system programming using Go (golang)

    Shashank Teotia
    Shashank Teotia
    Senior Consultant
    ThoughtWorks
    schedule 4 years ago
    Sold Out!
    90 mins
    Demonstration
    Advanced

    With Google Go becoming more popular and accepted, it becomes important for us to know the right framework to apply for adopting a TDD and CI approach to writing application written in Go. Especially, when we are talking in the context of writing software which interfaces with system drivers and services.


    We will also look at how we can create a build pipeline to run automated tests and continuously integrate into a packaged software.


    Other programming environments, have achieved a good level of maturity with tools for writing tests. I will present how we adapted our learnings in such environments into development in golang.

  • Liked Tarang Baxi
    keyboard_arrow_down

    Tarang Baxi - The Agile ContraDictionary

    Tarang Baxi
    Tarang Baxi
    Principal Consultant
    ThoughtWorks
    schedule 4 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Inspired by 'The Devil's Dictionary' by Ambrose Bierce, this is a satirical look at common misinterpretations and misunderstandings of Agile principles, processes, behaviours and roles. Precise, clear (re)definitions for Exactimation, Scrumudgeon, Abuser stories, Kanband-aid, Fragile methods, ScrumLord, Rundown chart, and many more!