2018 Defining Software Engineering Technical Review 
Scrum.org
NOVEMBER 24, 2021
Some Product Owners are highly involved with their teams, whereas others consider their work done when the product “is defined”. Julian Bass and his colleagues (2018) investigated which core activities Product Owners spent their time on in ten multinationals. This includes training, technical support, and preparation for new releases.
Scrum.org
OCTOBER 19, 2022
Before we begin, we need to define some of the terms we will use throughout this post. Throughout this post, we define them as “all users, customers, and other people or groups who have a clear stake in the outcomes of what this team produces, and invest money, time or both in making sure that happens”. The first term is Stakeholder.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MAY 10, 2019
Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.
Herding Cats
MAY 11, 2019
Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. De Meyer, C.
Leading Answers
JUNE 9, 2019
These websites and software services will only be “done” development when the company stops being competitive, offering new services or keeping up with technology evolution. At one time getting to "Done" on your software project was a relief, a goal, a milestone, now it is more of a tombstone. October 2018.
MPUG
OCTOBER 15, 2020
You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for one PMI-PDU and the technical category. A team lead or a technical lead, or a project lead. Now, audit is random.
Leading Agile
JUNE 7, 2018
Review the Story. Let’s review our first Story before we proceed: blog-ci-cd-pipeline-cloud-3.html. Why not define “saying hello” to mean that the microservice knows how to respond to an inquiry such as, “Dear microservice, do you understand version 1.0.0?” You just did TDD.
Expert insights. Personalized for you.
206 
Let's personalize your content