• Liked Daniel Zen
    keyboard_arrow_down

    Agile Engineering Javascript with Jasmine & AngularJS, Karma & Jenkins

    Daniel Zen
    Daniel Zen
    schedule 3 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.

  • Liked Michael Heydt
    keyboard_arrow_down

    Applying Lean UX to Capital Markets - Lessons From a Year of Lean UX on Wall Street

    Michael Heydt
    Michael Heydt
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Lean UX approach to interaction design is a spectacular model for defining and implemented what is needed in appications to support the users in their jobs, as compared to technical deliverables that in the end often do not meet the needs of the users.  In this talk, I will go over strategies for applying lean UX practices to capital markets projects, adapting UX to agile processes, including executing user interviews, rapid UX design, mockups to UI prototypes, and rapid implementation through continuous delivery and end user experience / acceptance testing.

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

  • Liked Todd Little
    keyboard_arrow_down

    Mythbusting Software Estimation

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Estimating software projects has proven to be particularly challenging. Over-running schedules happens frequently in our industry. Todd will look into some of the reasons for these challenges by exploring a number of myths of software estimation and then setting out to validate or bust these myths.

  • Liked Jez Humble
    keyboard_arrow_down

    Why The Project Paradigm Kills Innovation, and What To Do Instead

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Projects were invented as a vehicle for managing civil engineering projects. But software has completely different characteristics from, say, a bridge. In this talk I'll explain why the use of projects causes significant dysfunction, and how to build innovative products and services at scale based on lean principles.

  • Liked Todd Little
    keyboard_arrow_down

    Mythbusting Software Estimation

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Estimating software projects has proven to be particularly challenging. Over-running schedules happens frequently in our industry. Todd will look into some of the reasons for these challenges by exploring a number of myths of software estimation and then setting out to validate or bust these myths.

  • Liked Jez Humble
    keyboard_arrow_down

    Why The Project Paradigm Kills Innovation, and What To Do Instead

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Projects were invented as a vehicle for managing civil engineering projects. But software has completely different characteristics from, say, a bridge. In this talk I'll explain why the use of projects causes significant dysfunction, and how to build innovative products and services at scale based on lean principles.

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

  • Liked Karthik Sirasanagandla
    keyboard_arrow_down

    When Agile becomes Fr-agile..learn your lessons the fun way!

    Karthik Sirasanagandla
    Karthik Sirasanagandla
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate
    So you have heard of "Code Smells". Did you hear of "Agile Smells"? Yes or No; then this session is for you (us).
     
    In this session, Karthik intends to talk about the very many things that go wrong in companies that attempt to be or become Agile.
    But fault-finding is the easiest thing. Can Karthik provide concrete solutions? Yepp, he intends to share the solutions as well for most if not all the problems.
    And in same breadth seeks to know what others has to offer from their experience.
     
    Piquing your interest? Are you wanting to get a taste of some of the Agile smells? Below are some of them:
    * Belated Stand-ups
    * Non-participative stand-ups
    * War-zone Retrospectives 
    * Unfruitful Sprint planning meeting
    * Zero-Test development
    * Inverted Test Pyramid development
    * Gate-keeper QAs
    * Hierarchical Roles
    * Velocity Driven Development
     
  • Liked Puneet Sachdev
    keyboard_arrow_down

    Biting the Bullet - CMMi Level 5 Assessment for Agile Programs

    Puneet Sachdev
    Puneet Sachdev
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    CMMi Level 5 assessment has been a necessity and a hygiene factor for any service organization. Our organization has been assessed at Level 5 continuously since 1999. However, with spread of Agile methodologies in offshore scenarios we were faced with a question of ensuring CMMi compliance in Agile programs.

    This session will delve into details of our CMMi journey for Agile programs and how NIIT Technologies successfully got re-assessed at CMMi Level 5 with Agile in August 2013. The session will talk about various mapping of agile practices with CMMi process areas, identified gaps and how these gaps were addressed to ensure a successful assessment without diluting the Agile promise. 

    Some examples of how various process areas have been mapped to various agile practices. The session will be mostly example based and experience sharing. 

    Example 1 (Level 2 Maturity)

    CMMi Requirements Management PA talks about bidirectional traceability. If you go to sub practice (SP 1.4 of Requirements Management PA) level then there are three requirements: 

    • 1) Maintain requirements traceability to ensure that the source of lower level (i.e., derived) requirements is documented.
    • 2) Maintain requirements traceability from a requirement to its derived requirements and allocation to work products.
    • 3) Generate a requirements traceability matrix.

    Looking at the above, we managed this through requirements management being done in Agile projects using tools like Rally, TFS (agile templates), Jira Greenhopper and NIIT's internal agile management tools. These tools provide traceability from Epics --> Stories --> Tasks --> Test Cases --> Defects. This fullfils the intent of the PA. Hence we do not explicitly generate any RTM especially for agile projects (3rd bullet above) as the intent is already met. 

    Example 2  (Level 2 Maturity)

    CMMi Project Monitoring and Control (PMC) PA talks about a goal "Manage Corrective Actions to Closure" (SG2). This has 3 separate sub processes

    • 1) Analyze Issues
    • 2) Take corrective Action 
    • 3) Manage Corrective Action

    All these have been covered through the Agile practice of having "retrospectives", which happen regularily in Scrum. Retrospectives is where the people point out issues amongst other things, discuss what actions can be taken to improve and/or address the problem at hand. These action items coming out of retrospectives are then tracked as they would normally  have been done to closure. We do not mandate any specific format/tool for capturing and tracking this information.  

    Example 3 (Level 4 Maturity)

    CMMi Organization Process Defintion PA, has a goal for "Establishing Performance Baselines and Models" and a Sub Practice "Analyze Process Performance and Establish Process Performance Baseline".

    Here instead of taking traditional  metrices like productivity (hrs/FP), schedule slippage etc. we have taken metrices which are more close to the agile process. Examples of these are: 

    • 1) UAT Defects per Engineering Effort Unit
    • 2) Velocity Improvement over time
    • 3) % of story point change to measure requirements stability   
  • Liked Bhuwan Lodha
    keyboard_arrow_down

    Building a Team Backlog: The Power of Retrospectives

    Bhuwan Lodha
    Bhuwan Lodha
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    “Inspect and adapt” is one of the basic tenets of continuous improvement, and agility in general. Holding retrospectives is one of the core processes that allows teams to look back and reflect on their progress. However, over time, teams may focus only on the product work and lose interest in their own improvement as a team. Kanchan Khera and Bhuwan Lodha believe that one approach to solving this problem is to bring the rigor, structure, and discipline we use for maintaining healthy product backlogs to team improvement by creating a “team backlog”—items the team needs to do to improve itself. The team backlog introduces three keys to successful and sustainable team improvement—a structured framework, visibility of its impact, and creative ways for building the backlog. Just as a healthy backlog is the basis for a great product, so a healthy team backlog helps create great teams.

  • Niranjan N V
    Niranjan N V
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Usage of Agile methodologies such as Scrum, Scrum-XP, FDD, Crystal and methodologies has become increasingly large in IT Industry and also non IT industries. As the usage of agile methods becoming wide spread, the effectiveness of implementation of these agile practices in projects, organizations become more important for success of agile. Agile manifesto and 12 agile principles, acts as guiding principles and helps in the agile deployment. But when it comes to operational daily tasks, there is no method to ensure whether agile projects implement 4 values of manifesto. For traditional methods of software development we have standards such as CMMI,ISO etc. This paper makes an attempt to defining Maturity Model for agile projects.

    Following maturity model has been defined after our experience in consulting and training agile methods.

    Level

    Categorized by

    Guidelines for Description

    Maturity Rating based on Focus Areas

    1

    Basic

    1) Following traditional Water fall approach for delivery. 2) Agile practices used in pockets. 3) Requirements/Features (Product backlog items) are more at high-level or Epics levels

    Any Focus area <= 50%. Overall Compliance <=50%

    2

    Managed

    1) Product backlog items are broken from EPICs   into development user stories, product back log grooming is done 2) Basic metrics used and not very strong in prediction of the current performance, timeliness of deliverables 3) The Agile team delivers business value occasionally

    All Focus Areas - 50% and 75%. Over-all compliance- 50-75%

    3

    Matured

    1) Iteration Status , Agile Metrics in place using Agile Tasks Board 2) Usage of historic data such as velocity, story points committed v/s delivered for forecasting and estimation 3) Team reports the Iteration Effectiveness, Release Effectiveness to different levels of management like functional manager, Product Owner and Top management. 4) Team is skillfully using the Agile Engineering Practices in projects if not at Program Levels

    All Focus Areas - >75% Overall compliance > 75%

    To validate the maturity levels defined, an assessment of agile practices in projects are done and mapped into following focus areas.

     

    Focus Areas

    Development Practices/ Infrastructure

    Iteration Planning/ Tracking

    Product Ownership

    Release Planning/ Tracking

    Team Cohesiveness( Collaboration)

    Agile Testing Practices

     

    In order to rate the maturity levels for any project, the compliance of agile practices are mapped into above focus areas and Radar Chart is plotted to depict the compliance of each of these focus areas and are the agile mturity in projects.

     

     

     

     

  • Liked Prabhakar Karve
    keyboard_arrow_down

    Inspect and Adapt – Powerful technique to increase productivity through continuous improvement

    Prabhakar Karve
    Prabhakar Karve
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    Inspect & adapt is an important agile practice. Inspection helps us to see the reality beyond our filters. Better awareness of reality helps us to more effectively re-plan our work and modify our existing way-of-working.

    There are multiple benefits of this practice, but in this workshop we focus on how it can lead to continuous improvement in productivity.

    Inspect and adapt can be used while carrying out regular work activities across the entire agile life cycle. However our focus will be on the Scrum ceremonies and common artifacts.

    In this workshop, through discussions and exercises, we explore Innovative ways to expand our capability to carry out inspection & adaptation, without adding any extra overhead.

    During the session you also get a few simple yet powerful tips which can be practiced immediately once back from the conference.

  • Liked Zaheerabbas Contractor
    keyboard_arrow_down

    Applying Agile Practices in the Refurbishment/Modernization of my housing society

    Zaheerabbas Contractor
    Zaheerabbas Contractor
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the rush to be a proud owner of a large independent penthouse apartment in a huge housing society I did not realize (or did not want to) the actual reason behind this good bargain!

    I ended up being party to the following list (product backlog) of pain areas (or business needs) of the society members:

    • 1.Need of Generator backup to cater to the frequent power cuts at least for the common areas and lifts (I had bought my condominium on the top floor and could realize the pain!) – Must have and High Cost
    • 2.Modernization of the ageing lifts across 18 buildings (thanks to the substandard quality lifts which I realized when I started staying there L ) – Must have due to high risk however huge Cost
    • 3.Need for the CCTV Camera – Must have considering the frequent untoward incidents
    • 4.Seepage and septic tank upgrade
    • 5.Pavements, speed breakers
    • 6. And the list goes on….

    This resulted into the society being least valued in that area and no ROI for the members who had invested in the society.

    The society committee members were clueless on where to start (prioritizing with business value) with the given evolving budget and how to manage the timeline.

     Through this report, I intend to share how I utilized following Agile practices to overcome the challenges faced by the society members for its refurbishment and converted the society into one of the most sought out society over the period of few milestones (releases)!

    • 1.Prioritization(MoSCoW) of the backlog by agreeing up urgent need of the society in the given budget
    • 2.Continuous planning and re-prioritization of product backlog
    • 3.Outcome(Value) based agreement with various vendors
    • 4.Managing discipline in the acceptance criteria and retrospection (i.e. PWD lift inspection and approval for lifts functioning with the given municipality specifications and taking learning to replicate the same for future enhancements)
    • 5.Delivering end to end(INVEST) in the production in short releases ( i.e. one lift modernization end to end and commissioning of Diesel Genset end to end through incremental approach)
  • Dipesh Pala
    Dipesh Pala
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Intermediate

    Breaking up User Stories can sometimes be as painful as a relationship break up - but it does not have to be like that!

    Our experience has shown us that the key to getting full benefit from introducing Agile is in how the project work is broken up. When it gets difficult to see how to write small enough user stories, teams often resort to technical story cards. While this can give the team visibility of the work that is being done, the business is not seeing potentially implementable product, or early delivery of business value.

    This talk will dig a lot deeper to expose the real reasons for splitting up user stories and not just talk about doing it as a good practice - we must BE Agile not just DO Agile!

    Using real-world examples, this talk will also offer a set of guidelines and some unconventional ways for breaking up larger chunks of work into valuable user stories that can help Agile teams become more successful.

  • Liked Maris  Prabhakaran
    keyboard_arrow_down

    Coaching Mantras for Agile Team

    Maris  Prabhakaran
    Maris Prabhakaran
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    15 valuable Mantras which will crate value for Agile Team .

    These mantras are implemented and created value for the Agile Team

    Mantras for Product Owner

    Mantras for ScrumMaster

    Mantras for Agile Team

    Mantras for Agile Coach

    Learn Global Mantras from the session.

     

     

     

     

     

    10

  • Liked Binoy Shah
    keyboard_arrow_down

    Path for Effective Project Planning in AGILE

    Binoy Shah
    Binoy Shah
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Agile development has slowly and steadily made its way into the
    software industry. With increasing competitive pressure, Agile
    development helps an organization to churn out working software
    faster, thus adapting to changing business demands and generate a
    competitive advantage. There are however a few misconceptions
    about Agile software development. One of them is that there is
    little or no planning done in Agile. In this paper, we aim to dispel
    this myth.
    Planning a software implementation project in Agile, is similar to
    planning a project in any other software development
    methodology, however it is fundamentally different. As opposed
    to extensive, up-front planning required in other methodologies,
    agile planning simply follows an incremental approach to
    planning, just like agile development. This requires an initial
    planning to be done during earlier stages of the project and
    iteratively revisit the plan as we make progress and gain more
    insights during implementation.
    Agile Planning though incremental, strongly follows the
    principles of the “Iron Triangle of Project Management”. The
    triangle of project management is structured around the three
    vertices of Scope, Cost and Time. In this paper, we have
    attempted to break the entire agile planning process in 7 steps.
    Also we have depicted how each of this vertex is defined in its
    respective phase. We have also discussed some best practices to
    define each vertex of the Triangle and how the three vertices are
    connected to create the Iron Triangle, which is termed as Release
    Planning in the Agile world.

  • Dipesh Pala
    Dipesh Pala
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Once upon a time, Martians and Venusians met, had happy relationships together and accepted their differences to work towards delivering a project. Then came Agile and amnesia set in! ScrumMasters and Product Owners forgot they were from different planets. All of a sudden, Product Owners, ScrumMasters and the team members found themselves sitting around a table discussing user stories and potential solutions.

    This unprecedented access and communication created a whole new set of challenges… Sometimes it feels like our team members are from different planets, as if one is from Mars and the other is from Venus. You may have heard of Mars and Venus in the bedroom but this presentation will be talking about Mars and Venus in the team room.

    Based on my many years of experience in coaching and working with people in these roles, this presentation will describe why and how ScrumMasters and Product Owners react differently to various situations in a team room. The key is in understanding how ScrumMasters and Product Owners think and operate.

    And if ScrumMasters and Product Owners are from different planets, does it make sense for the two roles to be performed by the same person? Or does every Agile team even need both of these roles? Attend this talk to find out!

    This talk will further explore how we can counteract the differences in the communication, the emotional and the business needs of the two roles, and tips and techniques to promote a greater understanding between these two of the most important roles in any Agile team.

  • Liked Sheshadri Shekhar
    keyboard_arrow_down

    Facilitating truly effective "Individuals and Interactions"

    Sheshadri Shekhar
    Sheshadri Shekhar
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Agile Manifesto is largely predicated on communication within the project context. Truly effective communication is a function of trust and empathy. 

    This presentation shows the use of a behavioral assessment model in the context of “individuals and interactions”. We first trace the formation of a behavioral-type (or pattern) and then see typical behaviors exhibited by the 15 types identified by the model. We examine the role of behavioral-pattern in creating trust within the team.

    Following this we examine the response of each personality-type to "change". As agile coaches, we have noticed that the response to the change varies from active-support to passive-resistance to active-resistance. We use the DISC model the interpret the reasons for the response.

    Finally, we try to interpret behavior of the "team" using the DISC model.

     

  • Liked Raghavendra S
    keyboard_arrow_down

    Continuous integration and delivery for Better predictability

    Raghavendra S
    Raghavendra S
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The successes of agile software development lies in delivering the workable unit of application with quality as per accepted sprint timelines and receives feedback on the shipped deliverable and incorporate the changes in the current sprint to ensure greater customer satisfaction and trust. Believing in the fact that catch early and fix issues leads to a greater predictability in software deliverable, it becomes imperative to enable developers with set of tools and accelerators which can be leveraged during development. A well-defined continuous integration and delivery process plays a vital role in enabling project teams to leverage all the tools and accelerators during development and automating the testing processes.

    However, configuring and managing a CI system at an organization level for each project is a cumbersome task. Also, writing build scripts to automate build actions requires considerable scripting expertise and time. A centralized CI platform that can abstract the complexities of configuring, managing a CI workflow along with the build scripts can ensure greater predictability of software delivery at a far lesser time. Such a platform enables automated build definition creation, to execute build application at regular interval with list of validation embedded along with the compile and build operation. The platform intended to deskill the build definition creation, ensure compliance to continuous integration process. The list of validations that could be part of the continuous integration are automated code analysis, unit testing, code coverage, deployment to multiple environments, functional, performance, security testing, etc. and organization specific validations.

  • Liked Daniel Zen
    keyboard_arrow_down

    Agile Engineering Javascript with Jasmine & AngularJS, Karma & Jenkins

    Daniel Zen
    Daniel Zen
    schedule 3 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.

  • Liked Jayaprakash P
    keyboard_arrow_down

    Agile doesn't improve quality. Can we release a world class product?

    Jayaprakash P
    Jayaprakash P
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    There is a common concern by management that Agile doesn’t make a difference to the product quality. How do we release a product of world class quality?

     Problem is two folded:

    1. 'Definition of Done' is not created with Quality in mind, nor is it measured against the quality set at the beginning of the project.
    2. Quality Goals and subsequent adherence ensures quality is met and not just meeting 'Definition of Done' (DOD) criteria. For example DOD may be met, but quality may still be poor if not managed appropriately. How – lets discuss this through the session.

     Once the quality goals are defined for a project, Definition of Done should align with these quality goals.

    At McAfee, we have released world class quality products through Agile Methodology and Quality Best Practices together. One exceptional method we practice is by defining and tracking "Effective Quality Goals" for each sprint, and at every release.

    By driving agile projects through quality goals, we have products with ZERO defects deferred / logged by customers, 90+% code covered through automated test, 70% defects found early through development practices. This magic was not in just one project, but close to a dozen projects in the last 3-4 quarters.

    In this presentation, we will explain about how we changed the paradigm in the last 2 years and released world class quality products in a short span of time.

  • Liked Michael Heydt
    keyboard_arrow_down

    Applying Lean UX to Capital Markets - Lessons From a Year of Lean UX on Wall Street

    Michael Heydt
    Michael Heydt
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Lean UX approach to interaction design is a spectacular model for defining and implemented what is needed in appications to support the users in their jobs, as compared to technical deliverables that in the end often do not meet the needs of the users.  In this talk, I will go over strategies for applying lean UX practices to capital markets projects, adapting UX to agile processes, including executing user interviews, rapid UX design, mockups to UI prototypes, and rapid implementation through continuous delivery and end user experience / acceptance testing.

  • Michael O'Reilly
    Michael O'Reilly
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    Test Requirement Driven Development(TREDD) places a renewed emphasis on quality and accountability, and provides the insight to allow your product development and management teams to make the necessary changes in order to produce outstanding quality products on schedule, in a cost-efficient and highly collaborative manner.

    What separates TREDD from other development methodologies like TDD (test driven development), ATDD (acceptance test drive development), or BDD (behavior driven development), is the status of the test requirement when the product development lifecycle concludes.

    Test Requirement status is the breakthrough element that allows test requirement to provide an objective measurement to the quality of the product development team, so that adjustments can be made for subsequent product development iterations that will ensure quality improves, as well as increase the effectiveness of the product development team.

    Come and learn how your TREDD will catalyze your SCRUM team toward greater capabilities, quality, accountability, and satisfaction!

  • Mark Collins-Cope
    Mark Collins-Cope
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Intermediate

    This talk discusses a reference architecture for object-oriented/component based systems consisting of five strata (or layers**).

    The purpose of the talk is to show how this large-scale application model helps us to understand the overall structure of a system, how strata help us to clarify our thoughts, and how it encourages the separation of concerns such as the technical v. the problem domain, policy v. mechanism, and the buy-or-build decision - and of course why this style of architecture is relevant to ease of refactoring and software restructuring under changing and multiple requirement sets.

     

    Assuming an application is made up of a number of components, the strata proposed is based on how specific to the particular requirements of an application each component is. More specific (and therefore less reusable) components are placed in the higher layers, and the more general, reusable components are in the lower layers. Since general non-application components are less likely to change than application specific ones, this leads to a stable system as all dependencies are downward in the direction of stability, and so changes tend not to propagate across the system as a whole.

     

    ** regarding: layers
    As well as presenting the reference model, this talk also discusses and clarifies in concrete terms the meaning of one architectural layer being above another. Perhaps surprisingly, the meaning of the layering metaphor is the subject of some confusion. Specific examples of this are given in the talk - though not yet shown on the slides.

    (Note; this is suggested a 90 minute presentation however it can be extended to a full half-day, one day or two day workshop. I also have two other agile presentations which I can submit if interest is there - these cover agile planning).

  • Liked Naveen Nanjundappa
    keyboard_arrow_down

    Why not estimate? Think different for story point estimation.

    Naveen Nanjundappa
    Naveen Nanjundappa
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Agile Community talks a lot about Estimation and need for it. A large majority have different opinions, but when it comes to teams and organizations that are transforming to Scrum, mostly suffer in group estimation and story point estimation technique. 

    Agile primarily focus on value based deliver and that doesn't need estimation. 

    This presentation enrich those audience who need estimations for their project/product development, with details that make estimates better. At the same time it doesn't advocate estimation as a must have for product development.

    Following 4 aspects will be connected to story point estimation and help audience understand the story-point estimation.

    1. Concept of Accuracy and Precession

    2. Cone of Uncertainty

    3. Story point Estimation scale

    4. Group Estimation and Relative Estimation

    Teams struggle in estimating the product backlog items. Composition of estimation: any estimate is a mix of "the known, unknown and complexity". The presentation shall also connect estimation thoughts to product backlog and the cone of uncertainty

  • Liked Naveen Nanjundappa
    keyboard_arrow_down

    4 Quadrant: Focus Area based Team Retrospective.

    Naveen Nanjundappa
    Naveen Nanjundappa
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    The Regular and most popular retrospectives end with action items on the specific person in the team. 

    while the retrospective's primary goal is to enable the team to reflect onto themself and tune their behaviour for becoming more effective. In order to provide such a platform I practiced and coached 4 quadrant, focus area based retrospectives.

    In which the team focus on the over all improvement and not just an action item. this is truely the team's behavioural change and their actions to become more effective. 

    Based on many successful coaching experience, i would like to present this activity based session.

    Summary:

    The team identify the focus areas for improvements, then identifies the small delta improvement in that focus area that is measurable. then they decide on if they need external coaching or internally the team can achieve the goal.

     

    Focus areas | Coaching/Training

    _________________________

    Measurement | Self / team 

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Bare-Knuckle Web Development

    Johannes Brodwall
    Johannes Brodwall
    schedule 3 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 Sreekanth Tadipatri
    keyboard_arrow_down

    Help teams succeed, so that your business succeeds

    Sreekanth Tadipatri
    Sreekanth Tadipatri
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    This presentation discussess some of the factors that are critical to the success of the teams.  Successful teams is a prerequisite to a successful enterprise.

    What would help the team succeed?

    What would hinder the teams?

    What are some things that might work for the team, but might not work for an enterprise?

     

    The above is an example of what will be discussed during the session.

  • Liked Yashasree Barve
    keyboard_arrow_down

    Why can’t Enterprise have all the Fun? –Tales from Enterprisy DevOps Land

    Yashasree Barve
    Yashasree Barve
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the age of continuous deployments, where Googles and Facebooks of the world push newer features every now and then, without any down time to millions of users! Enterprises and Users of internal IT systems within Enterprise are still stuck with old time consuming processes that take ages to churn out new features to business. Why can’t Enterprises have this fun!


    This is a story of an Enterprise that adopted and got mature in its Agile Adoption. The sponsors could see value every sprint, but it took time to translate this value to end users. Drive to sustain agility as well as getting things out to end users quickly needed to take a great momentum.


    Experimenting with DevOps came as a natural extension to this Agile-Scrum adoption. We would like to talk about the how the idea of DevOps implementation in this Enterprise originated, the various challenges met at the initial stages, carving the road map and our journey. We would highlight the benefits that we reap out of this effort as well as share best practices from what we have learnt.

  • Liked Ganesh Samarthyam
    keyboard_arrow_down

    Refactoring for Design Smells - With Examples from OpenJDK

    Ganesh Samarthyam
    Ganesh Samarthyam
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Intermediate

    Refactoring has received considerable attention in the last decade given the important role it plays in Agile methods. With Martin Fowler popularizing ‘code smells’ in his classic book on Refactoring, most programmers know about smells. However, refactoring design smells and architecture smells is also equally important for creating high quality software. This presentation introduces important design smells and the refactoring strategies for addressing them. The talk includes interesting examples of design smells found in OpenJDK 7.0 (Open source Java Development Kit) code base.

  • Liked Samir Penkar
    keyboard_arrow_down

    What agile project teams can learn from marathon coaching?

    Samir Penkar
    Samir Penkar
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    Ever wonder how trainers coach marathon runners to run a distance of 26.2 miles or 42.1 kms?

    Chock full of incredible techniques and practical advice, this session will motivate everyone to expand their thinking on coaching agile teams for optimal performance.

    You will walk (or run) away with a fresh understanding of how you can inspire and uplift your project teams. As a running coach and SCRUM Master, Samir shares his insights into how you can affect small changes, inspire the right behavior and build trust among your team. You’ll learn how marathon coaches build endurance, stamina, strength and speed and how you can adopt these techniques for your project teams.

     

  • Liked Anuradha Gajanayaka
    keyboard_arrow_down

    Convincing Agile Estimation to a non-Agile Project board

    Anuradha Gajanayaka
    Anuradha Gajanayaka
    schedule 3 years ago
    Sold Out!
    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 Prerna Kale
    keyboard_arrow_down

    Cent Cent Business Value! A Sneak Peek at sprints from evolving design/UI, getting right priorities to delivering $$

    Prerna Kale
    Prerna Kale
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

     

    We want to share experience of working on a complex project, with deadlines set upfront and all players distributed. Perhaps argued as a complex combination to have but yet we were right there, on time enabling the new tool there. Reporting systems often have evaluation cycle that have imperative timelines to start and freeze, hence working for a huge system was not easy. Right agilist mindset with right agile practices helped us meet this. As a Product owner I jostled with eight experts using one system with some variation for their own service lines. We want to show how we leveraged the benefits of distributed teams balanced the challenges, kept the UI flexible enough to accommodate 8 expert reviews, and how our evolving architecture designed a system that had the most used and important features for the users to try hands on..

    Introspecting and sharing how we ensured Cent Cent business Value:

    - Kick off the project with eight stakeholders that got the ball rolling
    - Identifying the 30 % that was core to the business
    - Inspecting, and adapting to constant changes with modular designs
    - Getting stakeholder agree on priorities
    - Release Backlog with stories and design with validated acceptance criteria
    - Managing challenges and ensuring meeting needs seamlessly with truly distributed teams (Distributed PO/Designer/Architect/ Team/ Stakeholders)

    How important is it to dig the core 20-30% in projects with deadline upfront and ways to do that.. Prioritization techniques that enabled mutual agreement on the needs. Backlog with designs that reduced the development time. How work effectively with distributed teams, by building trust, keeping motivation and sharing the definition of done- yes we lived it and did it! We want the audience to explore it all with us and be open to take up and successfully meet the projects with distributed agile teams and tight deadlines yet agile :)

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    WORKSHOP- Defining Behaviors as a team

    Pradeepa Narayanaswamy
    Pradeepa Narayanaswamy
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

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

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

     

     

  • Liked Vinod Kumaar R
    keyboard_arrow_down

    Bending the hierarchy to ease agile transformation with new roles

    Vinod Kumaar R
    Vinod Kumaar R
    schedule 3 years ago
    Sold Out!
    20 mins
    Case Study
    Intermediate

    Hierarchy often comes in the way of Agile adoption and transformation. By hierarchy I mean not just the reporting structure but also how different functions interact with each other and how do they manage to work together on projects. Taking few lessons out of the book 'Maverick' by Ricardo Semler, I introduced new roles Associates, Co-ordinators and Facilitators in the team which was a pilot for agile transformation in an organisation. The outcome was a team like a football team with a common goal and individuals complementing each other in day to day work. I also made sure that they understand the difference between leadership and management, leadership can come from anyone in the team.

  • Parimala Hariprasad
    Parimala Hariprasad
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    Business stakeholders are always looking for ways to generate more business, and hence earn great revenues (or find the perfect exit strategy). Paying for testing comes last on the expense tracker. Some businesses work without testing teams because they see testing as mostly a drain on time and money. The typical executive perceives testing as a key bottleneck to product releases.

    In this session, Parimala Hariprasad shows how understanding the business model and business goals helps you test products better. She explains how to educate stakeholders about business risks. She explores ways testers can catch business blockers through early testing, and alert managers so they can be addressed quickly. This type of business information helps managers make better-informed decisions about the product early on. Some managers raise their eyebrows when first asked about their revenue models. Happily, once they see the value of business testing and how it could improve their revenue, they engage enthusiastically.

  • Liked Ankush Sabharwal
    keyboard_arrow_down

    Step-by-Step Process for Release Planning and Release Level Retrospectives

    Ankush Sabharwal
    Ankush Sabharwal
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    In the session two processes will be explained viz. Release Planning and the Release Level Retro. Step by Step approach will be discussed so that the same can be readily used in your Agile Projects.

    I have created these approaches of conducting effective Release Planning and Release Retrospectives in Agile projects. I have used these processes in various successful Agile projects.

     

    Note: Please refer to the Links section below to see the steps invoved in both of these processes.

  • Liked Abhishek Kumar
    keyboard_arrow_down

    How to implement TDD in DevOps : Right and Wrong

    Abhishek Kumar
    Abhishek Kumar
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    This talk will cover the pattern of following TDD when developing using Automated Configuration Management frameworks like Chef/Puppet. Real usability of Testing is based on keeping sanctity of WHAT needs to be tested WHERE. Talk will cover the same in domain of DevOps.

    This will cover the Concpetual Mapping of Unit Testing, Integration Tests and Performance Tests in reference of development under DevOps practices.

    The common mistakes that used to happen in DevOps domain was direct mapping of Business Application TDD model. Like porting of Testing tools such as rspec, cucumber for DevOps utilities and blindly implementing to show 100% coverage whether the Tests were actually justified there or not.

    We'll be seeing such examples and the correct way to implement justified Tests for your DevOps set-up.

    For example:

    Port of test packages like RSpec (puppet-rspec, chefspec) shall be used for only which cases and how they are totally un-justified for to plainly test the Resources which are just imitations without a real node.

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Coding with Geeks- De Code the secrets behind TDD, BDD and ATDD

    Vibhu Srinivasan
    Vibhu Srinivasan
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Intermediate

    This session is a coding sessiont that takes a problem and shows clearly what is the difference between TDD, ATDD and BDD. Ths session uses code for the server layer as well as UI layer.

    This session is not for you if you do not code. If you do code, please bring your laptop as we delve into the details of all these styles of programming techniques.

    We will rotate between ATTD, TDD and BDD periodically and show it at use in different layers. This session will be using Java , Rails, Scala and C# together so that you can see how you can benefit do these techniques even when coding in different languages.

    We look at common pitfalls and wrong beliefs that programmers have when it comes to these concepts

    This session is purely keyboard and you will have to bring a laptop.