Trouble Looms if you Wait to Define Future Out-of-Scope Items

In agile projects, where “just in time” is the key to waste reduction, why would I analyze what is and is not future scope? Two reasons are that it prevents 1) developers from adding unnecessary hooks and 2) differing assumptions about the size of the project. I will explain these reasons and suggest analysis steps in future posts.


About Bruce

Please see my LinkedIn profile:
This entry was posted in Expectations. Bookmark the permalink.

Please reply. Include your email or cell number to opt into my texts on these topics.

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s