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!

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

Outline/structure of the Session

1) Brief on the Contracts that traverse any project

2) Types of contracts and its need from FF, NTEFF, TM etc. 

3) What contracts (PSOW/ CSOW) to use when. - Knwo your client

4) Structure of a typical contract - overlay a typical Agile contract on top of it

5)  How agile can we be in our contracts and whats the benefit to the customer on that agility

6)  Do we need an MSA and legal intervention in agile projects

7) Customer feedback on agile or waterfall or hybrid

8) Does your development team know about the need for a contract.

Learning Outcome

1) The need for a proper contract to ensure visbility of the work scope in a project

2) The difference between a PSOW and a CSOW.

3) Where does an MSA fit in and is it always needed.

4) Project pitfalls when a SOW isnt available

5) How to define a SOW for an agile project - when we have to be AGILE and not restricted

6) The difference between a clearly defined DoD vs Acceptance Criteria.  Where does this fit in an agile contract

 

Target Audience

Senior PMs; PMO Leads; Corporate executives

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ellen Grove
    By Ellen Grove  ~  4 years ago
    reply Reply

    I am curious to learn more about this presentation, as I think that there are a lot of teams/orgs interested in the question of Agile contracts.  

    Will your presentation present contracts from real-world experiences?  I can't tell from the outline if this material is based on theory or practice.

    I'm also wondering if this a topic for the Scaling Agile Adoption theme, or if it's better suited to another stage - can you tell me how it relates specifically to this theme?  I'd also be interested in seeing an example of slides or video from one of your other presentations (or this one, if you've given it before)

    • Aruni Siriwardene
      By Aruni Siriwardene  ~  4 years ago
      reply Reply

      Hi Ellen,

      Yes, the presentation will talk about examples from real life contracts, where the understanding of HOW an agile methodology would work fro a project was discussed in a contract for the benefit of a client.  I will touch on aspects of a mix between waterfall and agile contracts.  Some clients are happy to go with it; others have various questions; this brings us to the question of just how much flexibility we can allow in a contract.

      Having read the description of the categories, this topic is best suited under the theme of 'Beyond Agile'.  The standard Agile recommended contracting methods will apply to most projects; but what happens to those projects that require agile as a development framework but not so much the initiation and terminations.  How do we extend a project and a contract to those varying needs?

      I'd be happy to share some of my prior work; do you want to send me an email address?

       

       

      • Ellen Grove
        By Ellen Grove  ~  3 years ago
        reply Reply

        Would it be possible to update your proposal with links to prior work (video, Slideshare presentation, blog posts) so that all reviewers have access to it?

        Thanks!

        Ellen

  • Vivek Vijayan
    By Vivek Vijayan  ~  3 years ago
    reply Reply

    It is a very different and interesting topic. The content seems to be concentrating only on Agile - so do you really want to say "waterfall enthusiast"? In case you would want to, then will the content have any linkage from the contracts in Waterfall world to Agile? I initially thought that the content would talk about that but could not find a linkage. 

    • Aruni Siriwardene
      By Aruni Siriwardene  ~  3 years ago
      reply Reply

      Hi Vivek,

      Thanks for your observations.  The need for the term 'Waterfall enthusiast' is based on the experiences i have had having to hand-hold clients from a standard waterfall approach down an agile methodology path when creating a contract for a project that is to be run on an agile mode.  Most clients who are very much 'into' Agile dont understand how we can work the 'T&Cs' of such an engagement that will ensure risk is managed on both sides, in a similar manner to waterfall contracts.

      If i could draw your attention to the "process" and "learning outcomes" section in the abstract, Process Piont 4 - talks about how we will discuss the nuances of an agile contract vs a waterfall contract; learning outcomes 1 to 5 will skim through waterfall methods in arriving at a distinction of the Agile contract.

      Trust this answered your questions

      Thanks


  • Liked Tarang Baxi
    keyboard_arrow_down

    Tarang Baxi - 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 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 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 Mike Burrows
    keyboard_arrow_down

    Mike Burrows - Kanban through its Values: An Agenda for Scale

    45 mins
    Talk
    Intermediate

    Introducing the Kanban method through a 3-layered value system - a familiar core that stimulates and drives change, a middle layer that is about direction and alignment, and a protective outer layer of discipline and working agreements.

    This humane, values-centric model aligns Kanban with the concept of the Learning Organisation and suggests ways to seek resonances with other methods. It has some practical benefits too: it can help us engage more effectively with the organisation as it currently is; it encourages us to self-reflect on our effectiveness as agents of change; it provides a convenient framework for the capture of stories.

  • 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 Abhilash Chandran
    keyboard_arrow_down

    Abhilash Chandran - Retrospectives with large projects and (or) multiple teams

    20 mins
    Experience Report
    Intermediate

    Retrospectives are the one of the most integral components of any agile methodology.  In scrum a retrospective is typically done after each sprint. This process is simple if team is small or only one team is working on a product. The problem starts increasing exponentially when many teams work on a single product. All the teams have ideas to improve the process and production.  One team may have an entire opposite idea of another. How to bridge this gap?

    Last project executed across different teams (onsite & offshore) and different departments was not a great success. How to learn from the past failures and apply it to future projects?

    In this discussion, I will be talking about some the points which can be easily followed in such scenarios. 

    Why did we did this?

    Normally in a scrum environment we have a single team with Product Owner; they do the retrospectives within team. Team identifies the issues and work on them. Many team falls into this category. It is pretty simple

    Let’s complicate this further.

    • A big product with 10 scrum team
    • Each Team has different PO

    Apart from these main stake holders there are many others who are interested in the success of this application

    • Sales team
    • Documentation team
    • UI design team
    • Architecture and performance team

    In such a scenario, a retrospective at team level will be effective only at granular level. But it leaves a gap in few areas; it helps to bring all the teams together for one big retrospective

    • Apply the improvements made at each team level to the whole program
    • A team's retro action item against the process followed by another team can be discussed at a higher level to find an optimal solution
    • Sometimes two team's retrospective action items may be contradictory. This gathering may point a third solution
    • Sr Product owners and manager will get all the teams together. A common focus and improvement plan can be shared across teams.
    •  All team gets to know about the key concerns at the program level and with other teams.
    • Ultimately it gave a feeling of one big family.

    My experience

    Last large retro organized in our group was a big success. The sales team & architecture team had many ley lessons to take back from this meeting.  Many issues were bought out which could have been solved with better co-ordination across team.  Concrete action plans were made by team for the subsequent release.  Some of the key findings were shared across other program teams also.

  • Liked Colin O'Neill
    keyboard_arrow_down

    Colin O'Neill - Achieving Enterprise Agility with the Scaled Agile Framework...and Have Fun Doing It!

    90 mins
    Tutorial
    Intermediate

    Scrum, XP, Kanban and related methods have been proven to provide step changes in productivity and quality for software teams. However, these methods do not have the native constructs necessary to scale to the enterprise. What the industry desperately needs is a solution that moves from a set of simplistic, disparate, development-centric methods, to a scalable, unified approach that addresses the complex constructs and additional stakeholders in the organization—and enables realization of enterprise-class product or service initiatives via aligned and cooperative solution development.

  • Liked Herry Wiputra
    keyboard_arrow_down

    Herry Wiputra - Crossing the T's and Dotting the I's

    20 mins
    Experience Report
    Intermediate

    The term "cross functional team" has been made popular by the Agile movement. In cross functional team, we put people with different roles to work together for a common goal/purpose.

    I have seen this worked really well in many agile teams. People are no longer on silo and everyone have better understanding what each other's role is and consequently, what each other do. This leads to better self organising within the team.

    However, I strongly believe we can take this concept to the new level. The concept of cross functional team should be extended to not just the team but also to the individuals within the team. Scott Ambler wrote an essay on "Generalising Specialist". The term T-shaped developer was introduced by Mary and Tom Poppendieck in her famous book "Lean Software Development". By nature, people don't like to get out of their comfort zone, hence the tendency to keep working in area that they are familiar with. When leaders can create an environment where everyone is encouraged to learn, grow and make mistakes, amazing things can happen.

    In my experience leading teams, I have witnessed many transformations that enabled individuals to go beyond their traditional role, such as a manual QA assuming Scrum Master role, a BA doing deployment, a developer doing QA for a story, etc. Not only this enablement help develop the individuals to widen their horizon and skillset, it also helped the productivity of the team through better collaboration. When a team reach this stage, we no longer have problems such as "The QA has nothing to do because there are no stories to test", "The developers have nothing to do because the cannot keep up", "The deployment took longer than expected because the Ops person was not aware of the special configuration".

  • 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 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.

  • 45 mins
    Talk
    Intermediate

    ‘One bad apple soils the barrel’ is a very true saying even in an Agile environment. Not identifying and managing poor behavior and performance can completely undermine any Agile transformation effort.

    How can Leaders, both within and external to Agile teams, set higher standards of accountability and hold people to it? Is self organization, peer pressure and the wisdom of the crowd enough to handle the wiles of organisational psychopaths?

    The fact remains that most teams will have a few difficult personalities and underperforming members.

    Agile is seen in many senior management circles as a softer, less accountable, way of working. Is that true?

    This talk will delve into how the human psyche works, drawing on latest studies in neuro and psycho analysis, combined with Harvard studies, to outline the best ways to define, identify and deal with ‘bad apples’ in an Agile environment while honouring the values and principles of Agile

  • Liked Archana Joshi
    keyboard_arrow_down

    Archana Joshi - How do I know if Agile is working for me or not? – An Executive’s Dilemma

    20 mins
    Experience Report
    Intermediate

    As Agile coaches, several times when we talk to the Sr. Management in a company to taking agile to a bigger level and adopt it across their business units a common response we get is "I have seen agile working for our project teams. I am also in midst of an agile transformation where we are applying it in large programs. But how do I know the transformation is helping me achieve my goals at an organizational level. Our organization typically tracks executives on finance, people & delivery parameters. In an agile context, how do I ensure that I am on track with the executive-level dashboard (finance, people and delivery)?" As part of this session, we plan to share our experience of how "Balance Score Card" technique was implemented at one of the financial services company following agile. By using concept of balance score card we were able to map the agile goals with the IT organization goals and ensure that the agile methods were giving the desired results.

  • 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 Natalie Warnert
    keyboard_arrow_down

    Natalie Warnert - Confessions of a New ScrumMaster

    45 mins
    Workshop
    Beginner

    So, you just got out of your CSM class, overflowing with your newfound Scrum knowledge and renewed faith in software development practices. You're ecstatic to share your new view of the world and show how Agile can benefit your organization, and you can't wait to get started. But, in your first Agile project, you meet resistance, opposition, and worst of all, modified Scrum practices. What's a ScrumMaster to do?

    Don't lose hope! You're definitely not the first ScrumMaster to meet these barriers, and you're not alone. I've encountered these situations in projects and have some tips to make the transition to Scrum easier on the team, the leadership, and you. Learn to overcome these problems in this interactive workshop and you become a better ScrumMaster and will help lead the team to the high performance you know they're capable of!

  • Liked Ram Srinivasan
    keyboard_arrow_down

    Ram Srinivasan - The Shared Mind: Essence of Interpersonal Neuroscience

    90 mins
    Workshop
    Advanced

    Why are some leaders socially adept while others show lack of maturity? Why some teams are high performing teams and others just are not? Ever wonder why people behave the way they behave? I did too.  As a coach, my quest to help teams collaborate better (and organizations create great culture) took me through an extraordinary journey through the maze of gamification, motivation, psychology, coaching, system thinking, organizational development and group process, and interpersonal neurobiology. Through this journey, I discovered why Lean/Agile principles are brain-friendly and how they help teams and organizations. In this session I share some of the insights that I have gained applying some of these principles coaching teams and organizations. You will also learn how you can share these concepts with other and gave teams and organizations a “language” to have crucial conversations, thereby increasing the system’s (team/organization) self-awareness.

  • 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 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.