Home

Pflogging

the never-ending quest for pragmatic solutions, useful plans, flawless execution, and designs that endure

Navigation

  • Create
    • Create content
    • Modify attributes
  • Navigate
    • Home
  • Site features
  • Areas of interest
  • Blogs
  • Quotes
  • Technology
  • Demonstration
    • View scheduled work for current day
  • Support
    • Contact me
Home Areas of interest Conventional wisdom

User login

  • Create new account
  • Request new password

A number of key features are only available to registered users. They include:

  • Access to the full content of top-rated material (only teasers are available to anonymous users after the material has been posted for 45 days)
  • The ability to search site content
  • The ability to access reviews of books relevant to site material
  • The ability to access key quotes relevant to site material
  • The ability to access content from partner sites
  • The ability to rate material
  • The ability to post comments
  • The ability to post new information and propose it for publication
  • The ability to request email notification when selected content is added or updated

Issue management

The orderly capture, isolation, and resolution of gaps between what exists and what could be

The objects of our affection

Submitted by Bryan Pflug on Sat, 10/25/2008 - 10:24.
  • Execution discipline
  • Change management
  • Issue management
  • Requirements-driven development

Concrete terms can also be specific or general. For example,

General terms and specific terms are not opposites, as abstract and concrete terms are; instead, they are the different ends of a range of terms. General terms refer to groups; specific terms refer to individuals—but there's room in between. Let's look at an example.

Furniture is a general term; it includes within it many different items. If I ask you to form an image of furniture, it won't be easy to do. Do you see a department store display room? a dining room? an office? Even if you can produce a distinct image in your mind, how likely is it that another reader will form a very similar image? Furniture is a concrete term (it refers to something we can see and feel), but its meaning is still hard to pin down, because the group is so large. Do you have positive or negative feelings toward furniture? Again, it's hard to develop much of a response, because the group represented by this general term is just too large.

We can make the group smaller with the less general term, chair. This is still pretty general (that is, it still refers to a group rather than an individual), but it's easier to picture a chair than it is to picture furniture.  read more »


  • Login or register to post comments

Judgements with justice

Submitted by Bryan Pflug on Sat, 10/25/2008 - 10:22.
  • Execution discipline
  • Change management
  • Issue management
  • Requirements-driven development
To discuss the use of dialog-based decisions across stakeholders, and trade studies, in order to achieve strategic and tactical decision-making without bringing development to it's knees.
  • Login or register to post comments

Defining what you love

Submitted by Bryan Pflug on Sat, 10/25/2008 - 10:08.
  • Execution discipline
  • Change management
  • Issue management
  • Requirements-driven development
About how to elaborate requirements
  • Login or register to post comments

Translating abstract needs into concrete actions

Submitted by Bryan Pflug on Sat, 10/25/2008 - 08:38.
  • Execution discipline
  • Change management
  • Issue management
  • Requirements-driven development
  • Risk management
Towards the lightPeople that are on a development project often use language whose meaning is ambiguous. Unravelling this lack of clarity be a tricky thing to do. Development relies upon effective communications, and achieving this foundational capability requires that all parties consistently understand the meaning behind the words that they are using. Such understanding usually requires careful listening, disciplined synthesis of concepts, and clear and written elaboration and allocation of derived details. Each of these steps involves conscientious and persistent attention in order to be successful.


 read more »

  • Login or register to post comments

My Vista horror story

Submitted by Bryan Pflug on Tue, 11/20/2007 - 10:15.
  • Issue management
  • Storytelling

Hamster wheel

This is how I spent over half my weekends and evenings from early April until early October, 2007, trying to get Vista to work as advertised. I had decided to upgrade to Vista in late February, shortly after it was formally released after a long and difficult series of public betas.  read more »


  • Login or register to post comments

Policies drive mechanisms - but not very far!

Submitted by Bryan Pflug on Sat, 07/21/2007 - 08:58.
  • Issue management
  • Requirements-driven development
  • Systems integration

Mechanic working on carI've been working for the past few weeks on several features of this web site that I felt were important:

  • The capability to aggregate RSS data from partner blogs and provide it on various views
  • The capability to provide visibility of content which is still under development when desired
  • The capability to subscribe to content and get email notification when it has changed

Such statements can form the start of functional requirements, but for me on this site, as in so many other situations, it's often first more fruitful to explore what's possible through prototyping and experimentation, before spending too much time trying to get the lower-level requirements right. This is particularly the case when the technologies you choose to use are unfamilar, evolving, or immature. In the case of the above capabilities, some required support from other open-source authors, some required changes on my web site host, and some were able to be done locally.   read more »


  • Bryan Pflug's blog
  • Login or register to post comments

Delivering product support that will thrill your launch customers and save you money

Submitted by Bryan Pflug on Thu, 07/12/2007 - 18:42.
  • Issue management
  • Quality management
  • Diagnosing

Microsoft has lost a ridiculous amount of money as a result of my having these problems, even after missing their launch date repeatedly. They have great vectors for supporting their many users, but had I been paying $65 for each of the phone calls (or even incidents) I made to Microsoft, I would have thrown up my hands a long time ago and migrated to Ubuntu (Linux distribution).  read more »


  • Login or register to post comments

Form a Chronic Issue Troubleshooting Team

Submitted by Bryan Pflug on Sun, 07/08/2007 - 07:45.
  • Issue management
  • Knowledge management
  • Quality management
  • Diagnosing
  • Filtering

x-ray on lightboardIn medicine, the term chronic disease is used to describe disease conditions which are long-lasting or recurrent, and indicates the course which a disease may take across a population. The term is used to distinguish such patterns and the required treatments from an acute disease, which has shorter treatment times, and typically more predictable treatments. Both chronic and acute diseases can have a range of severities.



The full text of the content which you have attempted to access is only available to registered users who are appropriately authorized and logged in. If you are registered, please log in with your username and password in the boxes on the upper left. If you are not registered, please use the link in that area to get an account. Finally, if you have misplaced your password, you'll also be able to request a new password there,



  • Login or register to post comments

The parable of the non-starting car

Submitted by Bryan Pflug on Mon, 01/22/2007 - 14:03.
  • Issue management
  • Storytelling
  • Surveying
  • Diagnosing

person on hamster wheelThere is a well-accepted body of knowledge that the repair time for problems increases the further away you get from the source of the problem. This is due to several different interacting situations:  read more »


  • Bryan Pflug's blog
  • Login or register to post comments

How to burn down problems before they burn you

Submitted by Bryan Pflug on Wed, 01/17/2007 - 19:41.
  • Execution discipline
  • Issue management

Turning problems into answersA problem is a questionable property observed during some evaluation or operation of a system. It may be reclassified as an anomaly if it's determined to be a nuisance, a failure if it’s determined that it affects operation of the system in an unacceptable manner, or a request for enhancement if desired functionality is in fact missing… but is always a distraction, if its root cause is difficult to isolate, if it cannot be duplicated, or if the problem is with the user, not the system. The problem may even become a feature if it turns out to be useful in some circumstances. Determining which of these paths is actually pursued is highly dependent upon how well the problem is written in the first place - and if you think that always is done well, read this.  read more »


  • Bryan Pflug's blog
  • Login or register to post comments

Copyright

Copyright © 2009 Pflogging
All Rights Reserved
RoopleTheme