The Problem, What strategies can we implement to prevent scope creep?, and What’s going on with tickets with client feedback? Why does some feedback seem out of scope for the ticket? This leads to scope creep, which leads to lost dev hours and money down the budget. Why is this happening? The Solution
It's no secret that working with Samvera has its own learning curves that provide a challenge for even the most seasoned Rails developers. SoftServ hears from a lot of institutions who have experiences developers on staff, but need some help with the Samvera-y pieces. SoftServ has responded to the Community need for training with a curriculum of hands-on workshops designed in consultation with Community members. The goal is to benefit the Community at large by equipping more developers with the skill sets to support the technology and sustain the Community. This talk will introduce the series and provide details about what participants can expect to learn.
We’ve all heard that the biggest challenges offer the best rewards. But we don’t always know how to tackle the large complex challenges that come our way. As a software engineer, I believe that learning how to break down projects and tasks is the most important skill we can have. In this talk, I will discuss some strategies that I have used to analyze, organize, and manage the projects that I have worked on. But don’t worry if you’re not a software engineer, these strategies can be applied to more than just software, including your personal and career goals.
and we often need to make localized adjustment(s) to address either an underlying bug or to extend existing behavior. The code-base has places for configuration, but sometimes that might not be enough. Join me on a foray into how you can make the Ruby/Rails changes you need now and not make things (too much worse) for your future self and others. and The Samvera stack is deep
