Distributed Product Owner Team for an Agile Medical Development

schedule Feb 27th 02:30 PM - Jan 1st 12:00 AM place Grand Ball Room

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.

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

Outline/structure of the Session

I have built up the presentation as a pyramid:

  • It's base is the background, what our product is about and which situation we came from
  • Then I tell you how we have grown a distributed PO team finding the right people with the right balalnce of knowledge and skills
  • How they communicate in the team and with the development teams,
  • including the use of communication and collaboration tooling (will be added in new slide set)
  • And on top of that the manyfold ways how they do customer collaboration

Learning Outcome

Learn how to find people with the right knowledge and skills

Learn how to set up the Product Owner team internal communication

Learn how to use effectively communication and collaboration tooling between Product Owner Team and Scrum Teams

Get to know many ways how to involve customers

Target Audience

Product Owners, managers, agile coaches, members of agile transition teams

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Sudipta Lahiri
    By Sudipta Lahiri  ~  4 years ago
    reply Reply

    Hi Andrea,

     

    I liked the experience that you have shared... just a couple of observations:

    a) Can you give some data - how many local product owners were working with a module product owner? Was this a hierarchical relationship or a matrix relationship? 

    b) What was the scope of your Daily Sync meetings vs the Weekly Sync meeting? Were you sharing some system or template to log and track the same?

    c) Any particular reason that you did not use Video Conferencing? I suspect that many teams may not have so much travel budgets.

    d) In the Customer Collaboration part of your slide deck, I couldn't take a clear learning out of this part. Of course, a product owners would need to meet customers, attend conferences, etc. That is the source of information for the Product Owner. Not sure if the audience will learn something new from this part of the presenation. Once again, some data would help. 

     

    I hope this feedback helps... :-)

     

    Regards

    Sudipta.

     

    • Rahul Sawhney
      By Rahul Sawhney  ~  4 years ago
      reply Reply

      Hi Andrea,

      Thanks for submitting the proposal!

      I have similar question as Sudipta about travel. Given that there are many collaboration tools available today, I am wondering how the cost for frequent travel (every four weeks) for remote product owners was justified. I am not saying that traveling is a bad thing, I am just curious  about the costs of this solution, its practicality and the returns it has paid. Also curios if you have considered and used remote collaboration tools and if they helped you in addressing cost and other issues.

      Thanks,

      Rahul

       

      • Andrea Heck
        By Andrea Heck  ~  4 years ago
        reply Reply

        Hi Rahul,

        thank you for your valuable feedback.

        Yes, I definitely need to add some page about the tools we are using, and for which meetings and how often we do by web based conferencing tools. We have an internal installation of Microsoft NetMeeting and use it with sharing slides, video, audio, working together on texts, remote debugging, remote common review of documents etc. We also have Communities of Practice for all roles cross-site, maybe I should elaborate on this also?

        We have the whole backlog shared in TFS and have a lot of transparency on the progress for the teams as well as for the Product Owner team.

        About travel: We have teams in several different countries. Especially in the first year it is very important that the Product Owner travels often, but this depends of course also on the distance, the experience the PO has with the culture in the country and the team, and the trust that has been built up. Building trust without a time spent together is not easy. It will pay off after a time. - I would not say that the PO has to travel all the time to the team, but especially in the phase where the local PO is trained and starts to acts as such, there is also close collaboration needed with the module PO, so both have to travel. Of course, also they have a lot of virtual meetings by web conferencing additionally.

        Best Regards

        Andrea

         

        • Rahul Sawhney
          By Rahul Sawhney  ~  4 years ago
          reply Reply

          Hi Andrea,

          yes that would support the proposal.

          Thanks, Rahul

    • Andrea Heck
      By Andrea Heck  ~  4 years ago
      reply Reply

      Hi Sudipta,

       

      thank you for your valuable feedback. Regarding your questions:

      a) this is between one local PO and 5 local POs, depending on the module. The relation is hierachical, so the module PO finally decides on prioritzation and trade-off decisions, but the local POs with time and experience are able to decide much on their own.

      b) I can elaborate more on this. The weekly sync has a common meeting protocol that is distributed in the whole project organization. The other meetings are more informal, or reults are documented in the discussed product backlog items.

      c) Oh, we do. I just note that when I say "virtual meetings", not everybody will recognize this as web based video conferencing. Maybe I should add a page for taking about the setup we have for cross site meetings, as we are using them quite often?!

      d)  Can you please give examples what kind of data would you like to see here?

       

      Thnaks and regards

      Andrea

       

  • Srinath Chandrasekharan
    By Srinath Chandrasekharan  ~  4 years ago
    reply Reply

    Hi Andrea,

    I have gone through the deck at slide share. Some questions

    • The section "Customer Collaboration" is an achivement / end result of your experince . To me it looked more like the challenges you have faced and hence should come in the earlier sections . Let me know
    • I could not see some of the typical challenges in distributed Agile like time zone differences, cultural differences. If these were there, how did you over come them
    • While the focus is on PO role, wre there challenges with the Scrum delivery teams as well. 
    • Were these distributed ?
    • What were other challenges from a logistics perspective. You have mentioned travel. Were there others like cost of communication etc.
    • With so many teams, were there integration issues ?
    • Also, on a generic note, the session you have is slotted for 45 minutes and there are about 30 slides ? In my experience, about 25 slides would be ideal for such this duration. 

    Please let me know your thoughts

    Regards,

    Srinath

     

     

    • Andrea Heck
      By Andrea Heck  ~  4 years ago
      reply Reply

      Hi Srinath,

      thank you for your valuable feedback.

      The section "Customer Collaboration" is one of three sections where I talk about the experience of our Product Owner team. - But if this seems to you and Sudipta like something others will not learn from, I can shorten that and add a chapter where I focus more on the cross-site communication and cross cultural topics in general, as far as the communication between Product Owners and their teams is concerned.

      In previous talks in the first years of our agile transition, I have tried to present all topics and aspects in one talk, but I came to the opinion that it is much better to focus on a main topic, and not try to explain everything we have done, are doing and have learnt in one talk. Therefore, now my main focus is the product owner team and how it has been evolving over time.

      At ScanDev 2013 in Gothenburg/Sweden, I also had a 45 min slot for this talk and there was enough time for questions at the end. At XP2013 in Vienna, I had a 60 min time slot, and went into more discussion with the audience, and this also worked out fine. In this time frame also others contributed some experience and asked very detailed questions. - Therefore, i would say I am well prepared to make it fit into 45 min with Q&A, even if I do the topic adaptions as I have suggested above.

       

      Thanks and regards

      Andrea


  • Liked Ryan Martens
    keyboard_arrow_down

    Ryan Martens - Beyond Agile Execution: Agility for Business and Impact

    Ryan Martens
    Ryan Martens
    CTO
    Rally Software
    schedule 3 years ago
    Sold Out!
    60 Mins
    Keynote
    Beginner

    Agile is not just a process change, its a mindset change for most. With faster time to market, better feedback and highly functioning teams, the Agile mindset opens our eyes to a better way of working as humans on large complicated and complex problems. Combining it with the concepts of Lean Startup, delivers another leap in team capacity and capabilities. It also opens the possibilities of using agility for more than just software development.

    Do you wonder how can we drive innovation in a disciplined way to tame our world's toughest problems? Can we apply the lessons learned from Agile and Lean Startup? Over the past three years, we've been able to apply agility at a new level, beyond business impact. Through our corporate social responsibility effort, "Rally for Impact", we aim to apply the agile mindset to mobilize citizen engineers to serve our communities and protect the planet. I want you to consider this growth path for yourself and your agile teams.

    Let's open the worlds mindset to a better way to empathize, explore and execute in these complex times.

  • Liked Jim McCarthy
    keyboard_arrow_down

    Jim McCarthy - Culture Hacking: The Prospect of Magnificence

    Jim McCarthy
    Jim McCarthy
    Founder
    McCarthy Technologies
    schedule 4 years ago
    Sold Out!
    60 Mins
    Keynote
    Beginner

    A culture is the set of shared attitudes, values, goals, and practices that both describes and shapes a group. The unique challenges of creating software have demanded totally new types of corporate culture. In response, we have created Agile, Scrum, and XP and many other cultural disciplines. These represent the birth of culture engineering and, although significant, are primitive compared to what will follow. Jim McCarthy introduces "culture hacking," a kind of cultural engineering that focuses on protecting personal freedom, extending openness, and embodying rationality. In the near future, a system made up of shared commitments and interpersonal protocols for hosting cultural innovations is likely to become available and standardized, leading to enormous personal and collective cultural and productivity gains. Happily, these gains will be based on culturally designed nobility of purpose, and a potent and virtuous cycle will continue to emerge, whereby profit derives from ennobled behavior. This cycle will lead to an era of widespread and abundant greatness - an era of unparalleled magnificence.

  • Liked Dave Thomas
    keyboard_arrow_down

    Dave Thomas - Unknown Knowns

    60 Mins
    Keynote
    Advanced

    In 2002, Secretary of Defense Donald Rumsfeld introduced us to the concepts of known knowns, known unknowns, and unknown unknowns. But he left out Unknown Knowns, things that we know without knowing it. And it turns out that these Unknown Knowns are actually the biggest category of knowledge - tacit knowledge.


    As developers, we work with knowledge: knowledge of the problem domain, knowledge of our tools, knowledge of our techniques, and knowledge of each other. So getting good at accumulating tacit knowledge is important.

    This talk will look at how we are poorly served by most of the current ways we are taught to be better developers. Can we do better? Only if we stop talking and start showing. Let's see why.

  • Martin Fowler
    Martin Fowler
    Chief Scientist
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    60 Mins
    Keynote
    Intermediate

    In the last decade or so we've seen a number of new ideas added to the mix to help us effectively design our software. Patterns help us capture the solutions and rationale for using them. Refactoring allows us to alter the design of a system after the code is written. Agile methods, in particular Extreme Programming, give us a highly iterative and evolutionary approach which is particularly well suited to changing requirements and environments. Martin Fowler has been a leading voice in these techniques and will give a suite of short talks featuring various aspects about his recent thinking about how these and other developments affect our software development.

  • Liked Rae Abileah
    keyboard_arrow_down

    Rae Abileah - Engendering Justice: Women, War and Peace

    45 Mins
    Keynote
    Beginner

    One in three women will be raped or beaten in her lifetime. Half of the seven billion global population are women so that means one billion women alive now will, or have been, beaten or raped or beaten. Women and children are disproportionately affected by war and occupation as well. And yet numerous studies illustrate how uplifting women's work and leadership can strengthen the whole society and economy. Women are at the forefront of global campaigns challenging militarism and violence, and working to redirect resources into health care, education, green jobs and other life-affirming activities. What can we learn from these women and their successes thus far? How can the technology sector support this crucial work? How do these social movements stay agile to rapidly respond to breaking news while building a long-term progressive movements for deeper social, economic and environmental justice? As Arundhati Roy said, "Another world is not only possible, she is on her way. On a quiet day, I can hear her breathing." In this talk, Rae Abileah will share visionary examples of women-led work for peace and justice and explore the paradigm shift needed for equality, human rights, and justice for all.

  • Liked Todd Little
    keyboard_arrow_down

    Todd Little - Leveraging Global Talent for Effective Agility

    Todd Little
    Todd Little
    Executive Consultant
    Accelinnova
    schedule 3 years ago
    Sold Out!
    60 Mins
    Keynote
    Intermediate

    A major challenge in agile development is the ability of test teams to keep pace with ongoing development while simultaneously ensuring that new development has not created regression failures. This case study from Halliburton shows how together with two globally distributed outsourcing partners they developed a comprehensive test automation strategy for their agile teams that effectively leveraged both in house and outsourced activities. This approach resulted in a significant quality improvement from prior releases.

  • Liked Ash Maurya
    keyboard_arrow_down

    Ash Maurya - How To Build Features People Will Want

    Ash Maurya
    Ash Maurya
    Founder
    Spark59
    schedule 3 years ago
    Sold Out!
    60 Mins
    Keynote
    Intermediate

    Most products fail. Not because we fail to build what we set out to build, but because we waste time, money, and effort building the wrong product.

    In this talk, I'll share our lean product development process that utilizes continuous customer feedback loops to ensure you don't go astray and instead build products people (will) want.

    What you'll learn:

    - How to track your your feature lifecycle on a validated learning kanban board
    - How to use qualitative testing techniques for early validation during the design and test phases
    - And then follow up with cohort based quantitative metrics to verify you have built something people wanted.

  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 3 years ago
    Sold Out!
    45 Mins
    Workshop
    Advanced

    As the popularity of Agile methods have grown, so have the misconceptions or myths associated with Agile also grown. These myths get even more glorified when we talk about them in the offshore or distributed context. And to make matters worse, you can throw in a fixed-price contract spanner into the engine.

    Worry not! In this fun-filled activity, we'll collect facts from the participants that they believe are true and then we'll declare them as confirmed or busted after an interactive (heated) discussion.

  • Corey Haines
    Corey Haines
    CTO
    Wavetable
    schedule 3 years ago
    Sold Out!
    45 Mins
    Tutorial
    Beginner

    Everyone has acronyms, mnemonics, and a list of rules to guide their everyday software design. In order to get the most out of these age-old gems, one needs to deliberately practices them. Rules are a good way to remind ourselves of these gems.

    Corey Haines emphasies his design guidelines in form of the "4 Rules of Simple Design." Attend this talk to understand the four rules and their importance in everyday programming.

  • Liked Corey Haines
    keyboard_arrow_down

    Corey Haines - Stories from 10 Years of Extreme Programming

    Corey Haines
    Corey Haines
    CTO
    Wavetable
    schedule 3 years ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    10 years ago I was introduced to Extreme Programming. Since then, I've been an avid practitioner, applying the techniques and values to my life as a software developer. Over that time, I've bounced between many extremes, learning and reflecting on the value that I get when building systems both for myself and for others.

    In this talk, I'll share some of those learnings and how my life as a software developer has changed with the times.

  • 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 Tarang Baxi
    keyboard_arrow_down

    Tarang Baxi / Chirag Doshi - A Practical Guide to Setting up Distributed Agile Projects

    45 Mins
    Talk
    Beginner

    A practical guide to setting up a new agile project team. Based on years of agile delivery and coaching experience for projects in a number of distributed and offshore models, for teams sized from 10 to 200 people, and spread across 4 continents, and 8+ locations. Some areas that will be touched on:

    • People - how to organize distributed teams, cultural factors to consider, ways to build trust, and how to avoid timezone burnout.
    • Process - how to communicate effectively, plan collaboratively, setup distributed practices (standups, retros, pairing, etc), effectively divide work on a common codebase, maintain visibility, and track progress.
    • Tools - (tips provided as a handout) which hardware and software tools should you absolutely invest in to help overcome communication,  visibility and collaboration challenges
  • Liked Mukesh Bhangria
    keyboard_arrow_down

    Mukesh Bhangria - Continuous Refactoring at Amazon: A Case Study

    45 Mins
    Talk
    Beginner

    Between the project deadlines, we always feel there is code which needs to be improved

    Usually Developers have the following 3 options:

    - Bite the bullet and do the refactoring as they go along.
    - Park the issue and address it later.
    - Allocate special time when the project gets out-of-control.

    As customer facing stories take higher priority, usually Developers are forced to choose the last option.

    However a team at Amazon took a different approach. Attend this session to listen to their first-hand story of how they changed this typical behavior to achieve Continuous Deployment on a critical service.

  • Liked Victoria Schiffer
    keyboard_arrow_down

    Victoria Schiffer - Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?

    Victoria Schiffer
    Victoria Schiffer
    Agile Coach
    SEEK
    schedule 4 years ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    I love being around awesome people, who build great products customers desire. 
    I love learning from and together with these amazing minds. 
    I love creating the right environment for teams to flourish. 
    I love change, and learning from new experiences. 
    I love working in Agile environments.

    How about you? 
    I bet there are some elements of this list why you're in Agile, too. And you can probably add even more elements to it.

    The Agile Manifesto states amongst others individuals and interactions, customer collaboration and responding to change.

    In our everyday life doing Agile we already respect these aspects in many ways. 
    But do we practice what we preach as best we can?

    I'd like to challenge your current way of thinking about people and processes. 
    I'd like to challenge you to focus on you, before you focus on others. 
    I'd like to challenge your current way of reflecting. 
    I'd like to inspire you to go different ways. 
    I'd like to inspire you to inspire others.

    In Agile we're already good in improving our processes and creating well performing teams and hence building the right things in the right way. And in the Agile Manifesto's communication and collaboration piece we can even get better.
    "You have not yet reached the limit of what you're capable of!" means we can always further improve. And we do follow this idea in our Agile processes, too, through continuous feedback (Retrospectives) and improvement.

    And why not take it even further? Why not go "Beyond Agile"?!

    Here's where aspects of Life Coaching come in handy: through also understanding and improving ourselves (how do we interact with people due to how we perceive our environment) we will even further improve communication and collaboration.

    Life Coaches believe our clients know the answer. And even if Agile Coaching is slightly different than Life Coaching, I see it as very relevant in Agile Coaching, too. If we apply this in Agile, instead of giving our clients (team, colleagues) the answers, asking them powerful questions to help them be more aware of what's happening at the moment, they will find their answer for it and will have a much better commitment to making the change for themselves, their teams and the company. It's not for us to TELL them what to do, but to ASK them what's going on for themselves. Here's where I see a huge chance for improvement.

    In my session I give lots of examples on how to link Life Coaching ideas to our Agile work environments. I've given the session at LAST Conference Melbourne and at the Agile Coaching Circles Meetup Melbourne. The audience was engaged and the attendees were very happy about having some new ideas on how to improve their daily work life.

    Come along to be inspired by Life Coaching and thus to benefit our Agile Thinking!

  • 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 4 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 Raja Bavani
    keyboard_arrow_down

    Raja Bavani - A Principle-Centered Approach to Distributed Agile (OR) Distributed Agile: Ten Guiding Principles

    Raja Bavani
    Raja Bavani
    Chief Architect
    Mindtree
    schedule 4 years ago
    Sold Out!
    20 Mins
    Experience Report
    Beginner

    The challenges in distributed agile can be seen under three broad categories viz., a) Communication and Coordination, b) Time Zone Differences and c) Issues related to People, Culture and Leadership Style. Successful teams consciously adhere to certain principles and it is their principle-centered approach that helps them face such challenges and deliver the best.

    Steven Covey wrote: "Principles always have natural consequences attached to them. There are positive consequences when we live in harmony with the principles. There are negative consequences when we ignore them. But because these principles apply to everyone, whether or not they are aware, this limitation is universal. And the more we know of correct principles, the greater is our personal freedom to act wisely." This is true in all situations of life and it includes application of agile methods in geographically distributed teams too.

    This session is to present the ten principles and elaborate 3-4 principles learned through experience in working with project teams and interactions with industry experts, and applied for more than a decade. These ten principles are above and beyond agile manifesto and agile principles. These are related to areas such as context-specific methodology, tools for productivity improvement, infrastructure for communication and coordination, knowledge management, focus on quality, inclusion, collaborative governance, automation, technical debt management, iteration progression and ensuring early success.

  • Liked Naresh Jain
    keyboard_arrow_down

    Naresh Jain - Scaling XP Practices inside your organization using Train-the-Trainer Model

    Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    90 Mins
    Workshop
    Advanced

    How do you effectively scale skill-based, quality training across your organization?

    Over the years, I've experimented with different ideas/models to scaling skill-based training across an organization. In the last 4 years, I've pretty much settled down on the following model. Its very useful when mentoring teams on skills like Test-Drive-Development (TDD), Behavior-Driven Development (BDD), Product Discovery, Writing User Stories, Evolutionary Design, Design Patterns, Problem Solving, etc. I've successfully implemented this model at some very prominent fortune 500 enterprises.

    The goal of this workshop is to explore what other successful models organized have used to scale skill-based training in their organization.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Tathagat Varma - Agile, Management 3.0, Holacracy...what next?

    Tathagat Varma
    Tathagat Varma
    Founder
    Thought Leadership
    schedule 4 years ago
    Sold Out!
    45 Mins
    Talk
    Advanced

    Pesentation deck is now available at http://www.slideshare.net/Managewell/what-next-31791295

    Modern management methods are still based on the then seminal work by Henri Fayol some 200 years back, followed by Frederick Taylor's work some 100 years back! Sadly, those models were predominantly based on industrial work, and don't really work that well in knowledge industry and today's sociological dynamics at workplace. Classical Agile methods codify several people practices that allow for a self-organizing team to evolve, but doesn't offer a lot of guidance on how to develop and groom leadership for agile organizations beyond a software team. Management 3.0 takes this issue further and develops it into a separate discipline altogether. On similar lines, Holacracy seeks to create social technology for purposeful organizations, though not specially targeting software organizations. So, the issue of leadership still continues to be unresolved and rather left to pave its way on its own. Unfortunately, when we want to achieve true end-to-end agility, it is not enough for software teams to be charging at top speeds but leadership not evenly matched to support them well in their endeavors. We clearly have a problem at hand...

    In this talk, we will study how the role of leadership has evolved and what does it look like for agile organizations at present. Many agile methods take an extreme view that limit leadership to team-level collective ownership of leadership. However, that might not be enough because of various reasons. In any non-trivial organization, whether a software organizations or any modern business employing software for business advantage, the reality is that organization units beyond a plain-vanilla software teams do exist. So, how does one go about grooming their top talent for playing an effective part in this process?

    Finally, we will also try to take a shot at some of evolving paradigms. For example, all these management thoughts are still based on the kind of outdated premise that an organization is based on 'boundaries' of operations. However, already we see that model being broken down, and the future teams look more like boundaryless entities bound with nothing but a unifying purpose that brings a bunch of volunteers together for a period of time. If our success increasing depends on such teams being able to effectively self-manage themselves, what role does leadership have to play in it, and are we getting ready for it? 

  • Liked Daniel Zen
    keyboard_arrow_down

    Daniel Zen - Agile Engineering Javascript with Jasmine & AngularJS, Karma & Jenkins

    Daniel Zen
    Daniel Zen
    CEO
    Zen Digital
    schedule 4 years ago
    Sold Out!
    90 Mins
    Tutorial
    Intermediate

    Agile & Test Driven Development of frontend JavaScript User Interface code is often passed over using the excuse that the UI code is "declarative" (What you see is what you get) and therefore does not 'need' to be tested. Others, will dismiss testing frontend AJAX code as too difficult to maintain or unnecessary because it is only important in context with the server. We will show how these misconceptions are false. 

    We will cover several popular JavaScript tools and technologies that make Agile frontend web development easy. We will show how these front end technologies cannot only be functionally tested, but Unit Tested. If time is available will cover Continuous Integration, Dependency Injection, & Mock objects.  

    By including your front-end code in your automated testing process you can prevent the inclusion of bugs that are usually only caught with manual testing.

  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    45 Mins
    Demonstration
    Intermediate

    "Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).

    Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.

    Our main question was: As mobile app developers, how should we architect/design our apps for CD?

    We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.

    If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.