Blocks I Have Met

Suggested definition:

Related topic: AgileSuccessfactors

Types of Blocks:

• Slow processes in areas related to project (but "process" is not part of Core Team)

• Inability of external groups to provide (quality) resources in timely manner

• Team engineering practices (relative to where they could be)

• TDD
• Version control procedures
• Build process
• Unwillingness to veer enough from mini-waterfall

• Quality of apprentices

• Some core team members not accepting Agile

• Lack of resources (non-people) (many sub-sets)

• Lack of specific people (for core team)

• Insufficient business commitment to the project

Naming Names (what's the priority list)

OK, now let's name names, and see what's the highest priority. I am thinking that we need to get specific, to make it actionable:

The fine art here is describing it (and getting at the root cause).

• teams are now able to make decisions faster, but unable to respond to them when they are dependent on outside parties working within the old time frames. Example: getting hardware or software takes weeks if not months.

• Config Mgmt needs to invent a faster process to build branches in multiple environments
• Environment Mgmt needs to build dev & various test environments more quickly
• Release Mgmt needs to make it much easier to put out a production release. Geez, we're trying to achieve Time To Market here!
• Damping rumors of Agile's perceived failure in specific projects
• Quality Services group needs to assign resources by system; should be for the project, covering multiple systems
• Reward system for the Team, not for individuals
• Better apprentices
• Developing some basic TDD practices in the teams (not talking automated tests yet)
• Unification of automated and "manual" test people in QS group. To enable projects to have both kinds of testing.

Comments on specific items

• How do we record differences of opinion on the priorities? Wording??

 Create your own business wiki!Support CommunityPublic, Silver wiki Privacy Policy RSS