Expert answer:rewrite by ur own words
Answer & Explanation:121212.doc
121212.doc
Unformatted Attachment Preview
Does it really make sense to jump directly into project coding and early prototypes in order
to discover ‘messes’ (unanticipated issues) early — that is, “to fail fast to success sooner?
Can this advice be implemented in a practical way?
No, it doesn’t really make sense to jump directly into the project coding and
prototypes to discover the mess in the operation system because there is no plan
has been setup where they are not sure if the coding was the problem so they might
waste of times and money in sources they don’t need it in their development project
and could the change be in unanticipated issue or other problems that need to be
fix. Without setting up a plan, might show unanticipated issue but I think it can
create plans to work with these unanticipated issues and not having the system to
be overrun. In the other hand, the prototypes project sometimes work to identify the
unexpected issues but is like creating the “Holy System” that has no errors which is
impossible to create the perfect operation where problems always face any system
so that’s we as IT people have to update them by correct the errors because of the
life changing in technology and people experience where we have to make our
project as the need in change so we can’t have the “No-Error System”.
However, this process of prototype project consider as Fail Forward by learning
for coding mistakes so they could avoid these failures in the future. Where I do
believe Fail Forward helps to have reflective practices in the project by understand
more about the analyzing performance to improve the system operation outcomes.
They also need to create a frame work and breakdown structure to discover the
messes that could lacked in the system instead of jumping into prototypes project
where it helps the IVK’s scope to define, improve, and follow the new
implementation.
Yes, I do think sometimes this advice can be implemented in a practical way if we
are sure to breakdown the structure of the project where we can see errors so we
could avoid them in the future if the system does not need any changes in the future
or re-design. But in the other hand if the system is have to in update and walk throw
with technologies changes, then I think we have to create a classic coding so we
could be able to do any changes and edit without prototypes.
…
Purchase answer to see full
attachment
How it works
- Paste your instructions in the instructions box. You can also attach an instructions file
- Select the writer category, deadline, education level and review the instructions
- Make a payment for the order to be assignment to a writer
- Download the paper after the writer uploads it
Will the writer plagiarize my essay?
You will get a plagiarism-free paper and you can get an originality report upon request.
Is this service safe?
All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades