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.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
Approval Process Pain Management
Gathering requirements is a fun job. But once they are gathered and documented, we have to get them approved before anyone can use them. Approval is important. We can do it the easy way or we can do it the hard way.
Consulting / Presentation / Requirements management software
Posted on:
Building the Case for Requirements Management Tools
Marcus Ting-A-Kee has assembled a great presentation on the value to his company of requirements management tools. In addition to creating the presentation and sharing it with all of us, he shares the process of creating the presentation in several articles.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Never Too Late For An Intermediate Timer Event
Business process modeling in the real world requires us to represent how processes deal with exceptions, delays and deadlines. Intermediate timer events can be used to model deadlines and the business processes for handling them. See an example of how to model a business process where two deadlines expire and the business responds.