Showing posts from 2017

Positive and Negative Space in Scrum

Negative space , in art, is the space around and between the subject(s) of an image. Negative space may be most evident when the space around a subject, not the subject itself, forms an interesting or artistically relevant shape, and such space occasionally is used to artistic effect as the "real" subject of an image. As an art major, I studied negative space and positive space in design. Here are some examples of negative space in design: By John smithson 2007 at English Wikipedia - Transferred from en.wikipedia to Commons by PHansen., Public Domain, The concept of negative space came to mind as I read a recent blog post from Ken Schwaber . This is his response to people asking for updates to Scrum, for example, to add Product Backlog Refinement as a prescribed ceremony: “Scrum is a general-purpose framework applica

Engineering Managers, Directors and VPs in Agile

Most guidance on Agile is directed at team members in such roles as Product Owner, Team Member (including developer, QA engineer, and UI/UX designer), and Scrum Master.  This leaves some with the impression that there is no place in Agile for traditional organizational leadership roles with manager or director titles. On the contrary, people in manager, director, and VP roles are essential to the success of an Agile organization.  To be effective, they need to practice discipline, discernment, and discretion Discipline – through Lean/Agile Governance principles and practices IT Governance happens, intentionally or otherwise.  Agile leaders should be deliberate in creating the right degree of formal governance for their organization that will allow teams to thrive.  A recent survey by Scott Ambler and Associates found that Agile Governance has a significant effect on creating conditions that allows Agile teams to thrive. Discernment – by participating in as many

Severity, Priority, Impact and Likelihood - Managing Defects and Risks

Defects and Risks are often dealt with in a subjective, emotional way.  That's unfortunate, because among all the things a software development team deals with, those are two that can be handled in a more constructive and empirical way. First, a couple definitions. Defect Severity: the degree of impact a defect has on system operation. A defect is something observed, so impact can be empirically quantified. Risk Severity: the degree to which a hypothetical event, should it occur, would impact system operation. A risk event is something that has not occurred, so impact must be estimated or extrapolated. The common element in both Risk Severity Assessment and Defect Severity is Impact on Revenue.  The FMEA framework that AKF recommends uses 1 = Low, 3 = Med, and 9 = High, to represent the exponential effect of a high impact risk or defect Impact on Revenue No payments being collected and/or payment data security compromised (Critical) Payment collection being de

Chatbot Code of Ethics

A  NYTimes article  describes efforts by a consortium of the largest technology companies to create ethical standards for AI. A related article in MIT Technology Review is titled  AI Wants to Be Your Bro, Not Your Foe . Artificial Intelligence has reached a level of sophistication, and is on the brink of being so pervasive, that we can have these serious conversations. In my work developing AI-powered chatbots to assist with learning, I work within the bounds of these 7 precepts: Right View - our chatbots honor humanity, human dignity, and the human quest for knowledge, understanding and technological innovation Right Intention - our chatbots promote human progress in the areas of intellectual pursuits and personal ethical development Right Speech - our chatbots use encouraging, prudent, and situationally appropriate language Right Action - our chatbots perform with integrity toward the aforementioned right view and intention Right Live