Lesson 25 of 40
Bring in an IDS and see exactly what it asks for
This video shows you how to bring an IDS file into Scope so you can read, organise and check what it asks for, instead of reading raw XML.
What you'll do
- In Scope, open Import, then Import IDS.
- Drop in the file and select Import.
- See each specification as a scope row, with its rules as requirements.
- Open Requirements to see what is asked for, from whom and when, and use AI to write any missing checking rules.
- Check the model against it in Verify.
Why it matters
Your IDS stops being a file people email around and becomes the plan everyone works to. You need the Manage Scope Items permission. The IDS goes into a single milestone, the one named in the file, so assign its requirements to other tasks afterwards if you need them elsewhere.
Common questions
Which milestone does an IDS import into?
One: the milestone named in the file. If there is none, Plannerly uses "Untitled Milestone", which you can rename.
How big can the file be?
Up to 5 MB, as .ids or .xml.
Discussion
0 comments
Sign in to start the conversation about this lesson.
Sign in