If you need to start a project, you’ve already failed #noprojects

schedule Mar 15th 03:45 PM - 04:30 PM place Grand Ballroom 2

I want to be controversial for a moment and propose an end to IT projects, project management & project managers. I propose that the entire project process is flawed from the start for one simple reason. If you need to run a project, you've already failed.

By definition, an IT project is a temporary structure to govern and deliver a complex change (such as a new product or platform) into an organisation. However, to be truly competitive, an organisation needs to be able to deliver a continuous stream of change. Managed properly, this negates the need for a project and the associated cost overheads.

This is fundamentally what #noprojects is. The approach, structure, tactics and techniques available to successfully deliver continuous change. At its core, #noprojects is predicated on the alignment of activities to outcomes, measured by value, constrained by guiding principles and supported by continuous delivery technologies.

This presentation will introduce you to #noprojects. You will learn how to define an outcome and create an Outcome Profile. You will also learn how to manage change within the context of an outcome through the Activity Canvas.

 
11 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

This is intended to be a practical discussion on how the run a continuous development process. There are four parts to the presentation (roughly a quarter of the presentation will be spent on each).

### Why #noprojects ###

They say the definition of insanity is doing the same thing over and over again and expecting a different result. We’ll examine why projects are not the best mechanism to deliver IT change. Specifically, within the context of 5 areas.

  1. Projects address a static need: Even the most comprehensive project leaves residual need which, over time, continues to grow and will lead to follow-on projects.
  2. Projects are expensive: There is an explicit cost to running a project. We will examine the three O’s that differ between continuous changes vs. a project; Overheads, Overruns and Opportunity costs.
  3. Estimates can be useful - but not accurate: The sad truth is that estimates (such as the duration of a project) are extremely hard to get accurate, and even harder to get right.
  4. Projects fail: As a consequence of the cost and difficulty in running projects, the failure rate of IT projects is extraordinarily high.
  5. Retention of subject matter expertise: There is a loss of knowledge when a project team is disbanded which also leads to additional costs for knowledge transfer to business-as-usual staff. This is implicit in the temporary nature of a project.

### The Outcome Profile ###

Whether at the level of team, division or organisation, the continuous flow of activities are focused on changing outcomes rather than outputs. An outcome is measured by its value to the organisation, whether direct & tangible or indirect & intangible. Outcomes are planned, slowly changing and define the common direction for the organisation.

The profile of an outcome defines the context, intent and expectations for the team, division or organisation. While the characteristics of a profile will differ between organisations, at a minimum it should contain.

  1. Summary – a short description of the outcome.
  2. Baseline Measure – if the outcome is quantifiable, what is the current state?
  3. Owner – who (either an individual or team) is accountable for this outcome?
  4. Dependencies and Order (Ranking) – where does this outcome sits in relation to your other outcomes?
  5. Investment – what is your maximum available investment/budget to achieve this outcome?
  6. Current target - what are you trying to achieve? Try to avoid percentages (as they can be easily gamed) and remember that this is a current target. It will change over time. Depending on the context of the outcome, the current target may also have a timeframe or due date against it.
  7. Outcome test plan - how will you measure effectiveness of the activities against the outcome target?

What is NOT included in the profile is a plan. The team is expected to dynamically react and proact (if that’s not a word, it should be) to opportunities in the market or organisation by instituting continuous change.

### The Activity Canvas ###

Organisations need a way to manage work without resorting to projects. That’s where activity management and the activity canvas come in. The activities delivered by each team to achieve an outcome exist on a continuum; small to large effort against low to high value. Your status quo (or do nothing) sits at the bottom left.

Activities in the ‘Do’ quadrant are relatively easy to perform and make measurable progress towards the outcome. Those in the ‘Defer’ quadrant are important, but complex, and need to be planned appropriately. The ‘Limit’ quadrant, usually your hygiene processes, should still be undertaken but only when needed or as time permits. At the bottom right is the ‘Avoid’ quadrant, and it would be rare for you to undertake any activities here.

### Bringing it all together ###

Without binding a team to a specific output, an organisation that understands, and plans for, growth outcomes can fundamentally adapt to a changing market. Governance controls come in the form of common working principles and clearly defined, non-conflicting, outcomes. In this way, senior management can delegate the ‘how’ to their teams, while retaining ownership of the ‘what’ and ‘why’.

Learning Outcome

  • Why #noprojects
  • How to define outcomes (rather than outputs) and use this as the key organisational driver of work
  • The structure of an Outcome Profile
  • How to use the Activity Canvas to manage a continuous flow of work
  • How to identify shadow projects

Target Audience

Project manager, scrum masters, IT managers

schedule Submitted 2 years ago

Comments Subscribe to Comments

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

    Most Organizations suffer, as they do not want to disturb the existing project management structure/project manager's. Wish this talk will influence the organizations in changing their thinking.

    45 mins is really short to change this thinking.

  • Naresh Jain
    By Naresh Jain  ~  2 years ago
    reply Reply

    Hi Evan,

    I understand this is an important topic and requires time to deliver it. However we generally discourage 90 mins talks (even for very experienced speakers.) What are your thoughts on involving the participants so they don't zone out? .i.e. turning this into a workshop/tutorial? Alternatively I would suggest reducing the time to 45 mins for a talk. 

    • Evan Leybourn
      By Evan Leybourn  ~  2 years ago
      reply Reply

      Actually, that's a fair point. I'll reduce this to 45 minutes and consider putting in a workshop/tutorial on Activity Canvas's.

  • ShriKant Vashishtha
    By ShriKant Vashishtha  ~  2 years ago
    reply Reply

    This should be the talk of the conference. Best wishes Evan.


  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 2 years ago
    Sold Out!
    45 mins
    Keynote
    Advanced

    On Agile teams, collaboration is the way of life. Our leaders want their team members to work closely with each other, have shared goals and even think as one entity. Why? Because we believe that collaboration leads to happier, more productive teams that can build innovative products/services.

    It's strange that companies use the word collaboration very tightly with innovation. Collaboration is based on consensus building, which rarely leads to visionary or revolutionary products/services. Innovative/disruptive concepts require people to independently test out divergent ideas without getting caught up in collaborative boardroom meetings.

    In this presentation, Naresh Jain explores the scary, unspoken side of collaboration and explains in what context, collaboration can be extremely important; and when it can get in the way or be a total waste of time.

  • Liked Pavan Soni
    keyboard_arrow_down

    Pavan Soni - Does Agile Approach kill Creativity in Organizations?

    Pavan Soni
    Pavan Soni
    Researcher
    IIM Bangalore
    schedule 2 years ago
    Sold Out!
    45 mins
    Keynote
    Advanced
    The key tenets of Agile Software Development, or Agile Development, are shorter timescales, close-teamwork, continuous improvement, continuous customer involvement, and quick response to change, amongst others. Whereas the key tenets of creative thinking are deferring judgement, divergent thinking, individual time-out, overriding customers' demands, deliberately introducing errors and serendipity, and valuing improvisation over improvement, including others psychological practices. It is seldom realized that some of the principles of Agility might be at the very cost of Creativity. Are they opposites or complementary? 
    I propose a temporal and spatial complementarity model of Creativity and Agility along with innovation process, from idea generation all the way to execution. Doing so, I caution the adrant adopters of Agility on the risk of not fully utilizing the creative faculty of humans, and propose ways in which agility and creativity can co-exist. 
    Based upon understanding the developments in the field of creativity and innovation, and contrasting the same with the Agile tenants, I propose a few areas where the two converge, and where they diverge.
    The insights are mostly drawn from viewing firms in action, and from cases studies of building a culture of innovation in the organizations. 
  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    What started off as a trial-and-error approach to improve the state of software development by a bunch of tinkerers, is today dominated by management consultants, "Thou-Shall" codified frameworks and rigid, expensive tools. Over the last 20 years, we've gone from, "I'm not sure, let's try this in a small-safe environment" to "you/your-team sucks; you guys have a very poor agile maturity because you are not doing _x_y_z_ (not conforming to the standards)." Along the way, we've lost the purpose of being agile .i.e. to embrace uncertainty and simplicity. Instead we've been forced to believe that consistency via top-down standardisation and predictability by increasing the rigour on process is our eternal quest. Anything that sounds simple and works 80% of the cases is discarded as being naive. What once drove thought-leader into agile, is now driving them insane. This is the unfortunate fate of Agile.

    Luckily there has been some fresh perspectives from Nassim Taleb, author of Antifragile. His work explains how some things benefit from shocks; they thrive and grow when exposed to volatility, randomness, disorder, and stressors and love adventure, risk, and uncertainty. More importantly why antifragility is beyond resilience or robustness.

    In this talk, I'll use some of Nassim's thoughts (and some of my own) to explain what is wrong with our current approach to Agile and how we can bring life back into Agile. Particularly how we can leverage Volatility, Uncertainty, Complexity, and Ambiguity to make product development more antifragile.

  • 20 mins
    Experience Report
    Intermediate

    The role of Leadership in organisation's Agile transformation is a critical piece. Yet many organisations struggle to find the right balance between top-down vs. grass-root transformation. I would like to share an experience where we were able to achieve fairly good grass-root movement, but had serious challenges building the agile mindset at the leadership level. While the leadership was trying to help with the best of their intentions, certain actions, behaviours and patterns did affect the spirit of agility. If you are keen to hear about typical leadership anti-patterns during agile transformation and some pointers on how to avoid them, this session is for you.

  • Liked Evan Leybourn
    keyboard_arrow_down

    Evan Leybourn - The Soft Skills in Software

    90 mins
    Workshop
    Beginner

    You’re probably here at this conference because you want to become a better developer, but I’m here to tell you that that you’re focusing on the wrong area. The difference between a good programmer and a great one isn’t the ability to write a kernel module in LISP, but the ability to communicate with your colleagues and customers. Skills sharing, collaboration and functional communication are critical for the success of any software project, and yet usually overlooked and undervalued.

    Developers who strive to be great, cannot afford to neglect their professional development in these areas. You don’t to reinforce the dreadful stereotype of the shy, stuttering, geek, do you?

    This interactive presentation will examine a few of the critical “soft skills” that are needed to thrive in corporate team environments. For example, how you can:

    • write effectively and speak clearly; i.e. get to the point,
    • move beyond your technical silo to work effectively as a team,
    • build trust and rapport with your project customers,
    • mentor, motivate and encourage others,
    • mediate or negotiate between competing points of view,
    • lead others and manage vendors
  • Liked Sean Dunn
    keyboard_arrow_down

    Sean Dunn / Chris Edwards - 7 Sins of Scrum and other Agile Antipatterns

    45 mins
    Talk
    Intermediate

    This is about agile “anti-patterns”: “something that looks like a good idea, but which backfires badly when applied” (Coplien). Todd has been around agile development from before it was called agile.  In that time, he’s seen teams fall into the trap of many of these anti-patterns, becoming stuck without ever realizing it. Frequently, this is due to a dogmatic understanding of what is right and wrong about Scrum and agile development. The first step to getting unstuck is to be able to detect these “sins.” The presentation aims to expose teams to these common pitfalls and then also provide a vision for a virtuous path to take them to the Promised Land.

  • Liked Chris Edwards
    keyboard_arrow_down

    Chris Edwards / Sean Dunn - The Value Uncertainty Game

    90 mins
    Workshop
    Beginner

    In this highly engaging workshop attendees will experience estimating, planning and delivering a new product and product features. The uncertainty in value and costs will be resolved through rolling dice based on the stories that the team selects and prioritizes.   The teams will run through 3 iterations of story cost, value estimation, and product feature delivery. Points will be scored for delivering product features and meeting release and iteration commitments.

    Dealing with uncertainty is one of the largest challenges that teams face. The simulation aims to have levels of uncertainty in value and delivery that are commensurate with those found in software development. Some of the key tools for dealing with uncertainty are integrated into the simulation.

    Attendees will come away with a better understanding of the challenges of working with uncertainty in software projects, and will learn some of the tools that are at their disposal for managing this uncertainty.

  • Liked Anand Murthy Raj
    keyboard_arrow_down

    Anand Murthy Raj / Sundaresan Jagadeesan - Philips - Enterprise SAFe Transformation Journey

    20 mins
    Case Study
    Advanced

    About the company

    Philips is a healthcare multinational company that focuses on building complete health care products and solutions for emerging markets, in addition to developing solutions and products for global markets, across the three sectors Healthcare, Lighting and Lifestyle. Using the expertise of its nearly 2000 engineers in Bangalore and aligning the marketing and sales teams the campus is responsible for creating and rolling out a complete set of products that include a whole host of solutions for global customers. It also contributes to global solutions in critical health care component development for connected consumer devices and renewable energy.

    Executive Summary

    Beginning of 2014, an external survey brought out the issues wrt time to market and code quality. Taking the survey results positively, the Leadership embarked on an Agile/SAFe journey with pilot projects. The results were amazing and with the currently learning from the pilots, the organization is running 25+ deployments within. The journey has started and Agile release trains are delivering periodic value to our customers at defined frequencies.

    Background Objective/Challenge

    Product quality, consistent & predictive delivery and quicker time to market are the key challenges the organization is trying to address today. Continuous Innovation is constrained due to the above issues and hence there is need to find a new way of product development which can meet the dynamic business needs, foster people engagement and deliver meaningful products to the world.

    Target

    ScaledAgile has been used as a framework for product development across the organization global. The whole organization is undergoing a transformation from waterfall way of working to the SAFe agile way of working and roadmap is till 2019.

    Agile Initiative

    The Framework used for the transformation can be summarized into 4 major steps

    1. Develop products in the Agile way with focus on Basic Agile practices (Scrum)
    2. Establish Product Ownership with focus on Enabling Scaling aspects (SAFe practices)
    3. Establish a release pipeline with continuous integration (supported by Automation)
    4. Adopt a DevOps Culture with focus on Continuous delivery (to production environment)


    This includes a comprehensive diagnosis of the various business processes, agile practices and behavior, engineering practices, delivery maturity and recommendations for the transition. A coaching and tooling plan is also an outcome of the diagnostics.

     Measurable Impact

    • Predictable Releases to customers (hitting the market with features every three months with features and business criticial bugs with less than 2 weeks with all the regulatory compliance)
    • Capitalization
    • Feature planned vs Feature delivered per program increment > 80%lose
    • Defect reduction co t 45%
    • Team velocity – Baseline vs actual.
    • Very high sense of ownership and high levels of engagement

    Transformation team Profile

    Global team

    • Agile Capability program manager -1 FTE
    • Agile Deployment Program Management – 1 FTE
    • Communication expert – 1 FTE (Today we are 0/1)
    • Coordination - 1 FTE
    • Enterprise Agile Coaches – 16 (Today we are 9 /16)

     

  • Liked Anuradha Gajanayaka
    keyboard_arrow_down

    Anuradha Gajanayaka - How to explore the Learning Organization within the Agile Organization

    20 mins
    Experience Report
    Advanced

    We have been discussing a lot regarding Agile transformations and how such transformations can help organizations. The key is to base such a transformation on the concepts of agility such as self-organization, intrinsic motivation, collaboration, etc. But still the puzzle of how those can be used in practice is less discussed. This is where the emerging concept of "Learning Organization" from Peter Senge can help a lot.

    The five disciplines of a Learning Organization lies in the heart of an agile organization. Therefore, exploring the learning organization within agile organization aids us find the "truly" agile organization.

    This is an experience report of a journey where a mid-size offshore software development organization moving towards to become a learning organization.  

  • Liked Pavel Dabrytski
    keyboard_arrow_down

    Pavel Dabrytski - Agile Economics: Contracts, Budgets, Capitalization

    Pavel Dabrytski
    Pavel Dabrytski
    Agile Coach
    Think Agile
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    How much does one story point cost? Is Sprint 0 an expense or an asset? Can you run Scrum with a fixed-cost contract? Agile challenges the existing approach to financial aspects of running projects: i.e. budgeting, forecasting, financial planning and vendor contracts.

    Applying new financial models becomes increasingly important for larger organisations adopting Agile. While they are going through an Agile transformation, they also need to maintain transparent financial governance and reporting. Shareholders would not be too excited about messy Annual Financial Statements.

    Join me if you would like to know more about Agile Economics. No financial degree is required and all the content explained in plain English with plenty of pictures!

  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Everything Is Better When We Stick Together: Building Team Working Agreements

    90 mins
    Workshop
    Beginner

    Whether a team is brand-new or seasoned veterans at working together, explicitly defining and/or refining a team working agreement will help the team to align on how they will work together effectively to meet their common goal. In this fast-paced hands-on session, participants will go through the process of building a team working agreement using LEGO Serious Play (LSP).

    Creating a team working agreement helps team members set the stage for effective communication and high performance by making assumptions about ‘what really matters to us’ and ‘how we will work together?’ explicit and negotiable.  Great working agreements address some difficult topics - what values do we share? how do we want to deal with conflict when it comes up? how will we handle problems within the team? - which are often challenging to discuss openly and honestly, especially when a team is first assembled.  

    This session will show you how to use LEGO Serious Play to encourage a frank and fearless discussion in order to kickstart these discussions so that a team can quickly create a powerful set of simple guiding principles for working together.  Participants will learn about the importance of team working agreements in creating team cohesion and common understanding of shared values and operational guidelines, and experience hands-on how to use the LEGO Serious Play cycle of build-share-reflect to have a participatory discussion to identify shared values, explore reactions to conflict, and build a set of simple guiding principles.

     

  • Liked Ran Nyman
    keyboard_arrow_down

    Ran Nyman / Naveen Kumar Singh - Large-Scale Scrum Introduction

    Ran Nyman
    Ran Nyman
    CEO
    Gosei LTD
    Naveen Kumar Singh
    Naveen Kumar Singh
    Professional Scrum Trainer (PST)
    agilemania.com
    schedule 1 year ago
    Sold Out!
    480 mins
    Tutorial
    Intermediate

    Large-Scale Scrum (LeSS) is a framework for scaling agile development to multiple teams. LeSS builds on top of the Scrum principles such as empiricism, cross-functional self-managing teams and provides a framework for applying that at scale. It provides simple basic rules and guidelines on how to adopt Scrum in large product development.

    In this tutorial, we focus on LeSS framework and see how you can scale Agile development to big organizations. We will start by looking at basic assumptions behind scaling and what different approaches there. Then we learn how LeSS deals with scaling in big groups and finally how LeSS can be adopted for existing organizations and what changes it bring in.

  • Liked Chris Edwards
    keyboard_arrow_down

    Chris Edwards - The Agile Architect: A Case Study in Transformational Leadership

    Chris Edwards
    Chris Edwards
    Senior Manager
    IHS Markit
    schedule 2 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    The role of “Architect” is sometimes frowned upon in the Agile community as a central command-and-control authority who bottlenecks decisions and limits team empowerment. Or at least, that is what we thought. Follow the real-life journey of our teams as we discovered how the role of an architect is compatible with Agile principles. We will explore our failures, and how we learned that an Architect can bring immense value to the organization through a focus on transformational leadership. In this presentation you can see how an Architect as Leader can help a project scale and can help create a truly self-sustaining organization.

  • Liked Sean Dunn
    keyboard_arrow_down

    Sean Dunn / Chris Edwards - To Estimate or #NoEstimates, That is the Question

    45 mins
    Talk
    Intermediate

    The #NoEstmates twitter hashtag was intended by Woody Zuill "..for the topic of exploring alternatives to estimates [of time, effort, cost] for making decisions in software development. That is, ways to make decisions with ‘No Estimates’."  Based on twitter traffic it has been successful at generating activity.  It's a bit debatable as to whether it has really spawned much exploration.  In this talk Todd will actually do some exploration using real data from over 50 projects at companies ranging from startups to large enterprises.  In addition to the analysis of the data, Todd was able to build a simulation model of the software development process to both replicate the data to and explore the conditions under which estimates add value and when they do not.  Based on the findings from the data and the simulations, along with an analysis of the types of business decisions that organizations need to make, Todd will provide some pragmatic advice for estimators and #NoEstimators alike.

  • Liked Krzysztof Czajka
    keyboard_arrow_down

    Krzysztof Czajka - How fudge candies catalysed feedback and engagement? Case study of successful experiment.

    20 mins
    Experience Report
    Advanced

    What is it about?

    This is a story about building appreciation and feedforward culture in the organization.

    I am going to talk about a bottom-up experiment based on Jurgen Appelo's Merit Money, conduced in the biggest e-commerce company in Poland - Allegro Group. It is a story about learning throughout an Agile experiment to get the most out of it. Primarily the experiment was intended to challenge the existing bonus system based on forced ranking. It turned into appreciation and feedback system with some sweets involved. 

    This feedback system has grown to more that 230 people involved from 3 different physical locations and still grows virally. We made a structure in which there is a coordinator in each location. If at least part of scrum team plays the game, SM is the first line contact. He distributes credits and exchanges them for sweets. Also cooperates with coordinator who is responsible for making sure system works well in his location.
    Iterations are now 2 weeks. We introduced a requirement that credit has to be filled in with short description what you thank for, in order to be exchanged. This was to promote written thank you’s and avoid situations where people hand over credits just to get sweets.
    Also every quarter we change credits appearance so that the previous credits cannot be exchanged for sweets. This is to set a time box and “flush the system”.

    Is it for me?

    Do you feel your team could be more engaged in their work? Trying to get rid of silos in your organization? Then this is for you.

    Get inspired by this simple game, in which there are several instant feedback loops, fun, gambling and sweet prizes.

    Oh, I forgot... and you'll find an answer on why we call it Fudge Candies.

  • Liked Kalpesh Shah
    keyboard_arrow_down

    Kalpesh Shah - Beyond User Stories - Taking your Team to Next Level of Awesome !!!

    45 mins
    Case Study
    Intermediate

    Great teams make great products, but what fuels this greatness? It's the common understanding and passion for the product but more importantly the singularity of purpose and the feedback loop and how the users are responding to the teams work. 

    The new world of product development is no longer about scope management and delivering the project on time and within budget but it's now more about hypothesis validation and learning from the users and their behaviors.

    The dynamics of product development is changing.  As more and more organizations are moving towards maturing their agile software development approach the traditional barriers of roles are being broken creating new opportunities and fostering a shift in the mindset. Instead of being tied down to scope management and delivering the project on time, Agile teams are focused and inspired by hypothesis validation and learning from the users and their behaviors.

    In this case study we will go over how a portfolio of 12 SCRUM Teams adopted a more outcome approach and how they shifted their mindset from project delivery in Agile way to adopting the Experiment-Measure-Learn-Repeat loop which plays a crucial role in teams overall motivation, performance and moved from being SCRUM Teams to "Product Teams".

    We will also see how we experimented with different team formats and how exposing the team members to different events and user research changed the way they perceived the information of the problem they were solving via features and user stories.

     

     

  • Fabiola Eyholzer
    Fabiola Eyholzer
    CEO
    Just Leading Solutions
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Inspired, empowered, and engaged people are the heart and soul of Agile – and HR.

    Transforming your organization into an agile enterprise is no small deed. And it does not matter where you are on your way towards embracing agility on all levels. There will be a time when you need to align your people solutions with the mindset and demands of agile people and organizations. We will talk about how to turn your Human Resources into Agile People Operations and boost your agility. 

    Join this session to

    • gain valuable insights into the world of Human Resource Management
    • recognize the impact of Agile HR practices through stories and examples
    • discover why Agile needs HR and vice versa
    • learn about People solutions in Agile Enterprises
  • Liked Dan R Greening
    keyboard_arrow_down

    Dan R Greening - Develop Agile Managers, or Agile Dies

    Dan R Greening
    Dan R Greening
    Managing Director
    Senex Rex LLC
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    We need good agile managers, if we hope to sustain rapid adaptation and innovation. Agile managers deliver coherent chunks of value, rapidly adapt to changing circumstances, and experiment with new approaches. Because they depend on their teams to support their own agile needs, they demand agility from their teams.

    Management talent is rare, and agile management talent even rarer. Gallup has surveyed thousands of managers, finding that low-talent managers, unfortunately a majority, create dysfunctional teams, build unsupported products and produce little sustained value. So developing high-talent agile managers matters.

    Agile managers adopt five agile base patterns for themselves: they measure economic progress, proactively experiment to improve, limit work-in-process by time and costradiate collective responsibility, and collaboratively solve systemic problems. It turns out these patterns have analogues in high-talent (non-agile) manager talents. That’s a relief, because we can focus agile manager development on extending the talents good managers already have.

    In this workshop, we'll explore agile manager characteristics, and management dysfunctions. We'll create approaches to move good general managers to good agile managers. We'll explore strategies for dealing with mediocre managers, whether they are peers or superiors. And we'll learning how to improve our own management agility.

    This talk comes from well-documented experience. I have held management roles from Team Lead through VP Engineering and CEO. At Citrix, Skype, Amway and other large companies, I used agile to help manage a 24-member user-experience department, three different agile coach teams and a 50-member data science department. Much of this work has been described in conference papers and detailed blog posts.

     

  • Liked Vipul A M
    keyboard_arrow_down

    Vipul A M - Building and Scaling a 100% Remote Team

    Vipul A M
    Vipul A M
    Software Developer
    BigBinary
    schedule 1 year ago
    Sold Out!
    20 mins
    Talk
    Beginner

    From 2 person Company that worked on the other side of the Globe,  to a 30+ company, thats spread across,  BigBinary has grown gradually.

     

    Since its completely remote as well as Service based, it has its own unique way of growing, and adheres to its own set of problems.

     

    There are things ranging from, how do you hire, when do you hire? To how does your client get comfortable with your Company being remote.

     

    As a team that can hire remotely, and pay good salary, does salary even account for a person to 

    join the company, when there is a looming reality that, there is NO Office, to this Company. 

    This is further exaggerated in an employer market like India, which is still fairly conservative.

     

    Or does a better work-life balance, no time wasted on commute, and being able to spend more time with Family, trump these concerns?

     

    Then, when new developers do join, how do you make sure that you are working in a sync, 

    as a team. Following the same Code conventions. Following the same process that has been in place 

    to ensure faster and better delivery.

     

    Since its remote, a 9-5 timeline is not a realistic or expected commitment. When should people work? 

    Does everyone need to be online and work at the same time? Not everyone is going to work on the same project or team.

    Does this apply to such teams in that case?

     

    How does the Company manage projects. Does it micro-manage the Developers? Because lets face it, 

    you are not sitting next to the person as in a office, you are not witnessing how the developers work. 

    How do you measure and build trust, in such a setup.

     

    How do you bring a developer up to speed, with exciting conventions and processes your company uses. 

    Things that are going to be alien to them.

     

    How do you pick concepts from the best, and then move forward as single team, functioning as a single unit, 

    instead of a bunch of freelancers scattered around.

     

    Lets discuss, some unique set of problems Remote Consulting teams face, and how to make most of it.

  • Liked Hugo Messer
    keyboard_arrow_down

    Hugo Messer - How to manage distributed teams successfully

    Hugo Messer
    Hugo Messer
    Entrepreneur
    Ekipa.co
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    In Hugo’s workshop, participants will create a best practice board in teams of 5-6 people. The teams go through each block of ‘The Bridge Canvas’. The goal is to share best practices, ideas and experiences. Per block, each team selects the ‘best best practice’. At the end of the workshop, each team will present the best best practices for each block.

     

    At the start of the workshop, Hugo shares a few best practices (personal ones + from other distributed agile experts). Each person gets a handout with clear instructions. This includes some questions to stimulate thinking within the team + some best practice examples per block.