Project planning for application development. What does an application for a diverse number of users need and what should one consider when coming up with product concepts and what tools should one use.

1. PROJECT
PLANNINGTOOLS
FORAPPLICATION
DEVELOPMENT
BY JOE SSEKONO

2. JOE
SSEKONO
SOFTWARE DEV
DEI TECH
@SSEKONO
01
02
03

3. PROJECTPLANNING
Every piece of development requires proper planning and
monitoring to ensure a solid application is the final products of
several days of work

4. 01 Identify and understand the
problem. Whether it is a
problem that belongs to a client
or one that society is facing and
may be in need of a solution
THE
PROBLEM
BUILD WHAT YOU KNOW

5. 02
Identify a team that would deliver and give the results desired.
Passion is a key factor when selecting a team since sacrifices will be
requred to make a good product
ASSEMBLEYOURTEAM
OFSUPERHEROES
AVENGERS OR JUSTICE LEAGUE

6. 03
DEFINESCOPE
A well defined project scope allows for proper planning. Don’t get carried
away by trying to integrate all cool new ideas or features all the time.
Otherwise, the project will never end.

7. 04
Set realistic deadlines for every phase of the project. Too much time
would create drag and room for losing the picture of the project; too
little time will create pressure and lead to several bugs
PROJECT
DEADLINES
ATTACH TIME TO ALL PHASES

8. 05 Create a pseudo solution for the
client through mock-up and
prototyping tools like balsamic
to create a process flow
PROCESS
FLOW
MAKE IT CLEAR

9. 06
GETMODULAR
Break your application into sections for easy building up by your team.
Identify what the front-end and back-end will be composed of. The more
modular the application gets, the easier it gets to modify. Through several
iterations, the process will be fine tuned

10. 07 Testing is a key aspect of
development. Test through each
process to ensure proper
functionality with given input
and expected output
ALWAYS
TEST
NO BUGS ALLOWED

11. 08
Engage prospective end users of
the project. This would aid
identify user experience issues
and also help find bugs and
study user behaviour
USER
ENGAGMENT
BUILD FOR YOUR USERS

12. 09
DOCUMENTEVERYTHING
Documenting helps during both development and maintenance phases of
a project. For instance, working with tools such a an issue trackers to help
document found issues found and to ease the distribution and follow up
on bug fixes among the development team

13. 10
Pick a communication channel that most if not everyone on the team is
willing to use to help in the collaboration of project tasks eg Slack, IRC,
Skype
KEEPCOMMUNICATINGAT
ALLTIMES
ROGER!!! DO YOU READ ME

14. 11
CODINGSTANDARDS
Come up with a coding standard that the team should adopt such that
every member on the dev team can easily follow when required to. This
would help in situation when one needs to modify of extend source code.

15. 12 Work with version control tools
for proper distribution of coding
tasks among the team members
with less worry about code
collusion. This also allows for
rollbacks
VERSION
CONTROL
SPLIT TOE

16. 13
Always plan for future iterations
in the development process. This
helps clear process flows and
creates efficiency in the creation
of features that had not been
planned for before
KEEP
ITERATING
LET DO IT ONE MORE TIME...

17. 14
LESSISGOOD...MUCHLESSIS
BETTER
14.DRY principle should be the pivot of project development. Rely more
on Object-oriented programming and also use existing tools and libraries
to carry the heavy load that would be required in building system features

18. TOOLS
Sketch book
Idea Board
Paper cards
Cloud docs (eg Google docs)
White Board
Redmine
Trello
Pivotal Tracker
REQUIREMENTS TASK ALLOCATION

19. TOOLS
Balsamiq
Lucidchart
Wireframe Sketcher
Slack
Skype
IRC
MOCKUP AND
FLOWCHARTS
COMMUNICATION

20. TOOLS
CMV Frameworks
API tools (Postman, REST)
Firefox Developer Edition
Neon
Eclipse
Netbeans
Sublime Text
FRONT, MID AND
BACK END
IDES AND EDITORS

21. TOOLS
Redmine
Mantis Issue Tracker
Pivotal Tracker
JIRA
Jest, Jasmine for JS
SimpleTest, Selenium,
PHPUnit fpr PHP
Jenkins for automated
testing
ISSUE TRACKING TESTING

22. TOOLS
Git
Mercurial
Helix VCS
VERSIONING

23. WHATWOULDYOU
LIKETOASK...
I DARE YOU!!!

24. THANKS
ALOT
0782120367 | @SSEKONO | SSEKONO@GMAIL.COM
BY JOE SSEKONO