James Kovacs shares a great insight on software testing and the software testing process. His epiphany about test driven development makes it obvious to all of us why this technique is so powerful.
Business Process Modeling
Posted on:
BPMN Diagrams – Hit the Links With Intermediate Events
Drawing business process diagrams can be tricky. Just getting the layout on the page to look good can be tricky. Intermediate link events can be used to clean up diagrams. They can also be used to jump from a specified point in one process to a specific point in another process.
Business Process Modeling
Posted on:
BPMN Diagrams – Intermediate Rule Events
Business process modeling is rarely applied to simplistic processes. Real world business processes often embody complex decision making. Complex decisions imply choices of action. Rule intermediate events, in BPMN, are designed to express these hard ideas with easy to read diagrams.
Agile / Software development
Posted on:
Seven Core Elements of Agile
Mishkin Berteig at Agile Advice writes an excellent essay on the seven core practices of being agile. Understanding these elements is the first step in getting past the hype and fud of the agility dilemna. Promoters of particular agile practices, as well as detractors use hyperbole and extreme examples to make their points. While very effective techniques for arguing, inspiring and motivating, hype and fud detract from learning, teaching and understanding.
Consulting
Posted on:
Customer Service and Software Development
Sometimes we forget that people use our software. Neil Mix reminds us that we should treat our users like people. For anyone who’s worked retail or food service jobs (like yours truly), we shoud treat our customers like customers.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Make It Right With Intermediate Compensation Events
Sometimes we can’t undo our actions. Water under the bridge. But we can make it right by doing something else to compensate. BPMN allows us to use intermediate events to compensate for mistakes in the past. A classic example is cancellation of a purchase. Our example is a little more fun.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Stop The Presses! With Intermediate Cancel Events
Business processes often need to be cancelled. An error condition can cause a process to terminate, or an incoming message can cause a process to be terminated. Error conditions occur within transactional subprocesses and a cancel intermediate event is used to describe any special cancellation steps.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Play Catch With Intermediate Errors
Business Processes might start out as easy-to-diagram simple processes. Over time, these processes get more complex, as they have to deal with real-world considerations and unanticipated situations. Things can go wrong. Classical flow diagramming gets complex when dealing with errors or exceptions in a process, while BPMN modeling keeps things simple.
Marketing / Product Management
Posted on:
Outside Reading: Product Manager vs. Product Marketing Manager
Jeremiah Owyang, a Silicon Valley Community Manager writes about the difference between product managers and product marketing managers.