Browsing All posts tagged under »Twitter«

Nearly four years ago we began the TAPUniversity Blog. It’s been based on a mix of our training and consulting delivery. The first topic was a top 10 things to do for contractors or consultants (or not do). After a round of consulting assignments, in pharmaceutical and insurance, with other consultants alongside me, I observed […]

Two years ago I entered the fray of open networker, or “LION‘s” in LinkedInjargon, for a two-week test before a series of presentations concerning pro-social networking to management and project management audiences. My networked ballooned from a rather healthy 750 to over 3,000. While generally innocuous, I soon found out that not having a “fake” […]

SWOT Analysis (Strengths, Weaknesses, Opportunities and Threats) is a venerable mainstay of management and MBA curriculum. While it’s typically applied at the organization level for strategic management, SWOT analysis can be a helpful technique for understanding the business perspective for a set of requirements or a project. It’s described in 9.32 of the BABOK™ A […]

The whiteboard. The dry eraser. The multi-color pens. The overbearing meeting participant. Those four things often come together when thinking of brainstorming. It’s a technique among multiple management nexus disciplines and at the heart of agile, business analysis and project management. It can produce great results from a team. The Business Analysis Body of Knowledge […]

Project teams are complex and it’s essential that the team works together productively to achieve the end goal. Every so often, there will be a ‘project maverick’ that upsets the balance. Perhaps they ignore the plan, or escalate an issue straight to the CEO. Mavericks are often seen as a Project Managers worst nightmare, as […]

Re·quire·ment n. 1. Something that is required; a necessity. 2. Something obligatory; a prerequisite.¹ Among the twelve principles of Agile, that one that evokes a good amount of debate is changing requirements, even late in development. This contrasts from plan driven approaches to development that “freeze requirements” and lock those in through development and deployment. […]

The four values of the Agile Manifesto (Individuals, Customer, Working Software and Change) are further elaborated in twelve principles. The first principle is “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. “ The first line provides the goal – satisfy the customer. That customer focus brings Agile […]