IT SOLUTIONS
Your TECHNOLOGY partner! 
-Collapse +Expand
Proj Man
Search Proj Man Group:

Advanced
-Collapse +Expand Proj Man Group Home

WEEKLYLESSON
Week 20 Lesson◄╣

MY
GROUPSETTINGS
-Collapse +Expand Message Board
-Collapse +Expand Proj Man KB
-Collapse +Expand Proj Man Study Test
PRESTWOODCERTIFIED
-Collapse +Expand Proj Man Store
-Collapse +Expand Members Only
   ► All GroupsProj Man Group   All Groups   Print This   

Weekly Proj Man Lesson

Week 20, Posted Monday 5/20/2013

Content changes every Monday @ 1AM!! Check back once per week. Learn! Review! Test Yourself!

Weekly Proj Man Lesson

[Print Lesson]

Week 20, Posted Monday 5/20/2013

Content changes every Monday @ 1AM!! Check back once per week. Learn! Review! Test Yourself!

FAQ of the Week
Question: When should I execute a change order on a time and material project?

Answer: At a minimum, execute a change order whenever the project budget will increase and when it will decrease by a substantial amount. Although not required, you should execute a change order whenever features migrate or are swapped out for other features. You should execute a change order even when the swap has no apparent impact on budget. I say "apparent" because analysts frequently do less research on changes especially when they look like they will have no impact on the budget.
Tip of the Week
Tip:

If you are a single developer, assign the artifact to that single developer and use it to track the completion of both the documentation of the artifact (requirement, design, and test script) as well as the building and testing of it. If you are part of a development team, assign the artifact to the resource gathering requirements and create additional tasks. If you want to track the building with a higher grainularity, add additional tasks.

Definition of the Week
Waterfall Process:  With the waterfall approach to developing software, one phase of the development cycle follows the other and the user is involved only at the beginning during the requirements gathering phase and at the end during the acceptance phase. The requirements gathering in the waterfall approach is critical and unless it is 100 percent perfect, the project will fall short. Other processes, including PSDP, involve the end user throughout the process ensuring a better outcome.
Link of the Week

None This Week
File of the Week

None This Week

Lastest Proj Man Flashcard

Our flashcards are part of our library of tidbits.

Tidbits are FAQs, Definitions, Tips, and Code Snippets from our knowledge base.

Q&A: UML and PSDP Artifacts
Question: How do PSDP Artifacts relate to UML Diagrams and other traditional software documentation?

Answer:

If you're doing full blown UML based requirements, then you may wish to not use the requirements section of PSDP Online. However, if you're just using UML Use Case Diagrams to document process, then you can use one PSDP Artifact per use case as a guideline.
Posted By Mike Prestwood, Post #100970, KB Topic: PSDP Artifacts
-
  Load Time=1 seconds.
 
Print This
-
 
Have a question? Need our services? Contact us now.
--Mike Prestwood

Call: 916-726-5675

email: info@prestwood.com


389 People Online Now!!  
Online Now: Sign In to see who's online now!  Not a member? Join now. It's free!
Show More...


©1995-2013 PrestwoodBoards  [Security & Privacy]
Professional IT Services: Coding | Websites | Computer Tech