Hi
user
Admin Login:
Username:
Password:
Name:
Turning stories into websites
--client
pyconau
--show
pycon_au_2016
--room Room_104 11367 --force
Next: 1 Intentionally Blank
show more...
Marks
Author(s):
Donna Benjamin
Location
Room 104
Date
aug Sun 14
Days Raw Files
Start
15:00
First Raw Start
error-in-template
Duration
0:30:00
Offset
None
End
15:30
Last Raw End
Chapters
Total cuts_time
None min.
https://2016.pycon-au.org/schedule/65/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Turning_stories_into_websites.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
The user story sits at the centre of most agile development methodologies. But what makes a good story? and where do stories come from? What do we do with them once they've been estimated, prioritised, re-sized and broken down? How can we maintain our sense of the big picture when it's broken down into tiny puzzle pieces? How does that help us build good products? This talk puts the focus on the "user" telling the story to understand their requirements for the product. It then turns back to the team to look at how we hear and discuss those stories in order to bring them to life to build the product, and build it right.
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review