Snusnubees
New Member
- Joined
- Jul 22, 2011
- Messages
- 1
- Gender
- Female
- HSC
- 2011
I need an example of PARTICIPANT DEVELOPMENT! Thanks
-
Finished your HSC? Check out our University Discussion, Non-School forums or help out next year's HSC students! -
YOU can help the next generation of students in the community! Share your trial papers and notes on our Notes & Resources page
Need example for a system development approach (1 Viewer)
- Thread starter Snusnubees
- Start date
Lwaxana
Betazed Ambassador
people who beta test games
Prototyping or Agile include participants.
Prototyping - devs produce something, demonstrate , users give feedback, devs improve, demonstrate etc etc until users happy. -
Agile - same but much more structured as devs work for 1-2 weeks - demonstrate - get feedback, decide what to incorporate for next cycle (1-2 weeks) etc etc until users happy.
Also there is a method not mentioned anywhere in the sillybus called "don't tell the guys in IT" where a user with hobbyist interests in ICT will write a small proggy/database to make life easier for him/herself at work, other see it & it spreads through an organisation - until eventually assimilated by the IT borg(great example of this was a user wrote a program to communicate with Telstra exchanges in the late 80's- it is still in use although to a lesser extent having been replaced by several specific systems)
Particpants CAN be involved in traditional waterfall method, but are used as Subject Matter Experts & tend to represent/liase with user management
Prototyping - devs produce something, demonstrate , users give feedback, devs improve, demonstrate etc etc until users happy. -
Agile - same but much more structured as devs work for 1-2 weeks - demonstrate - get feedback, decide what to incorporate for next cycle (1-2 weeks) etc etc until users happy.
Also there is a method not mentioned anywhere in the sillybus called "don't tell the guys in IT" where a user with hobbyist interests in ICT will write a small proggy/database to make life easier for him/herself at work, other see it & it spreads through an organisation - until eventually assimilated by the IT borg(great example of this was a user wrote a program to communicate with Telstra exchanges in the late 80's- it is still in use although to a lesser extent having been replaced by several specific systems)
Particpants CAN be involved in traditional waterfall method, but are used as Subject Matter Experts & tend to represent/liase with user management