Transcript of "Developing the next generation"

2.
Start with an idea….a simple app
 Come up with an idea and develop a plan that brings it
from idea to market.
 The idea has to be exciting for your team
 It does not have to be a million dollar idea to start with
or even be a brand new idea it just has to be an idea
that the team is excited about doing – the key is start.
 It has to be understandable – something your team can
relate to - after all they will be learning many new
concepts if they have to understand the theory behind
the app they are developing then you will lose them
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

3.
Epic
 Given that the app is singular in its function there really
is a single Epic with a number of user stories.
 Currently there is a single release being planned
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

4.
User Stories
 This first post is the start of the project and making sure
our product owner agrees with tomorrow is the discussion
with the production owner to make sure we are all on the
same page. We need to create our initial release plan.
 The team has been creating their user stories to share with
the Stakeholders.
 Since it is a mobile the intern acting as the UX Designer is
learning to use Balsamiq™ to define the screens.
 Then using plain text explaining the interactions with each
of the screens and the possible traversals.
 Finally arriving at the results and the reason for using the
app.
 Then complete the User Stories with non-functional
requirements or Technical Stories.
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

5.
Peer Reviews - Documentation
 Our process is informal
 Moderator – rotating so everyone can have the opportunity to lead a review
and learn how to solicit comments
 Author
 Inspectors
 Organizations define their Review Process from rigid and formal
including all defined roles.
 Some organizations have no Review Processes defined or informal
processes.
 Why do Peer Review
 learn the value of peer review
 how to give constructive criticism to their peer.
 how to take constructive criticism and understand it is not personal, the point
of peer review is the best outcome of the product.
 Create an environment that is non-confrontational or safe opening
where everyone can provide their comments it may be at an open
meeting or it may be later through email or even privately to the author
then shared. Learning to create an environment where everyone can
share their ideas can make everyone more creative and productive.
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

7.
Sprint Planning Meeting
 Overview of Agile
 Methodology that is based on iterative development
 Scrum is a lightweight process framework for agile
development and the most wild-used one.
 Sprint 1: tasks shared to allow interns to review and
provide more informed estimates at sprint planning
meeting
 Task assignments made
 Reviewed activities
 Reviewed validation criteria for tasks
 Discussed product decisions
 Set up first sprint Stand up
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

8.
Sprint Activities
 Sprint 1
 UML overview – included in the first task is to provide the
first iteration of the design
 Review of Sprint 1 status facing holiday challenges, travel
challenges one intern tracking to completion the other is out
of town.
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

10.
Version Control
 Decision: Git
 Requirements:
 Xcode – development platform
 Input from hiring managers from the technical industry
 readily available
 easy to download
 runs on Windows and Mac
 FREE initially
 Limited potential conflicts within files on merges.
 training material on the product website
 I would recommend reading for more information and
further comparison http://biz30.timedoctor.com/git-
mecurial-and-cvs-comparison-of-svn-software/ except for
their reference to only “man-hours” when I am sure they
have really meant “staff-hours” the story does a nice job
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

12.
Project in Transition…
 Why change the Platform from Sencha Touch to JQuery.
 After a lengthy attempt to use the Sencha Touch as the mobile app
framework the platform proved too unstable and difficult to use.
 The documentation for Sencha Touch was also limited and did not
prove useful even when a full license was purchased.
 At this time the JQuery is much more stable and there is much more
documentation available.
 There are many more code examples available
 JQuery mobile is not without its issues but many of them can be
worked around and the intern that was doing the development was
able to overcome the hurdles.
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

13.
Conclusion
 I am building these slides as this project continues week over week.
Coquisoft, Inc. has taken on 2 interns to prepare them for technical
jobs – both are graduating in the next 6 -9 months.
 There is some value in the slides as a way of sharing the
information there is also a more informal blog with additional
information that will support the slides on tumblr. Follow me on
tumblr and slideshare to see how the project turns out over the next
few months then download the app.
 Coquisoft, Inc has two apps on iTunes
https://itunes.apple.com/us/app/musicnode/id483593508?mt=8 is
free and https://itunes.apple.com/us/app/punch-buggy-
trip/id665685947?mt=8 which is $.99 where all of Coquisoft’s
proceeds to Mutual Ground Shelter in Aurora
 Follow me on tumblr mtemanuel to read the blog
http://mtemanuel.tumblr.com/post/69206090133/developing-the-
next-generation
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

14.
Lessons Learned
 The Project took about 2 months longer then expected
 Even if you put extra time in the schedule when the staff is all
volunteer life sometimes gets in the way.
 The schedule was not a priority it was the experience gained by
the interns on this project therefore at times it made more
sense to set it aside until adequate time to could be devoted to
the project and the learning experience.
 School was also a higher priority
 Making platform decisions
 There are several platforms and tools available and it is key to
select those that provide adequate documentation and support
 Software upgrades – during a long development cycle it is often
upgrades to something in the project and it will set you back
because it will be in compatible with something else.
 With mobile devices there are decisions around which platforms
to support
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net

15.
Project delivered
 The App is finished –
 It was delivered for the iPhone and is available in iTunes –
for Free
https://itunes.apple.com/us/app/rate-that-
movie/id903685421?ls=1&mt=8
A little about the App:
 Description
 Tired of guessing as to whether or not you will like a movie before you see it?
Do you also not trust movie critics to properly reflect your taste in cinema?
Then Rate The Movie is the app for you!
Rate That Movie uses a proprietary algorithm to determine if you will enjoy a movie
based on your personal tastes.
8/7/2014Michelle T. Emanuel mtemanuel@coquisoft.net