Not Signed-In
Which clippings match 'Software Development' keyword pg.1 of 2
19 SEPTEMBER 2014

Agile Software Development: what we've learned at Forty

"The general idea behind Agile is that instead of arguing about the wording of a requirements document written three months earlier with little perspective into the current situation, it's often healthier to acknowledge that the project is going to be flexible and evolving, and put processes in place that allow it to be that way.

Barely over 200 words, that manifesto become the foundation for a movement that has changed the world of software development forever. Endless writing and speaking has explored the various ways the manifesto could be interpreted, and many specific frameworks and methodologies (such as Extreme Programming, Kanban, Lean, and Scrum) have been developed to formalize its principles. A whole 'Agile industry' has emerged, with successful companies offering tools, training, consulting, certification, and other products and services. The economic engine behind the Agile movement as a whole is massive. ...

On the surface, it seems like design and Agile should magically work together, but there are some underlying philosophical issues you have to wrestle with before figuring it out. Design is all about big–picture thinking: planning, strategy, working out all the details, thinking everything through, making it perfect, etc. (Eric Karjaluoto called it the 'masterpiece mentality.') Agile, on the other hand, is more often about doing the basics and saving details for later: iteration, minimum viable products, 'perfect is the enemy of done,' etc. Those two worlds don't blend smoothly together, at least at first. Agile developers can get frustrated with designers for over–thinking things ('Why can't they just let it go? We can get to that later.'), while the designers get discouraged by the perceived low standards of Agile developers ('Don't you want it to be good? Don't you want the user to be happy?').

In both cases, though, the problem comes from a misunderstanding of each other's perspectives (as problems often do). The designer isn't being obsessive, they're just trying to do right by the user. And the developer isn't being lazy, they're just following a process that actually gets things done with minimal navel–gazing. Both sides could learn some important lessons from each other."

(James Archer, Forty)

1

TAGS

agile development • agile model • agile modelling • agile software development • current situationdesign processdevelopment life cycle • development methodology • Eric Karjaluoto • evolving needseXtreme Programmingfacing unpredicted challengesflexible management methodology • flexible process • formalised principlesiterative approachiterative design processiterative developmentiterative processjust-in-time (JIT)Kanban • Lean (methodology) • management methodology • over-thinking • perfect is the enemy of done • requirements documents • saving details for later • scrum software development processsoftware developmentsoftware development methoduser experience design (UX)UX designwaterfall modelwhirlpool model

CONTRIBUTOR

Simon Perkins
21 FEBRUARY 2014

Video Tutorial of OOP Design Patterns

Fig.1 Java Video Tutorial by Derek Banas, 19 August 2012.

1

TAGS

data abstraction • Derek Banas • design patterns • encapsulation • inheritanceJavamodelling language • object class • object-oriented designOOP • OOP concepts • OOP design principles • programming fundamentals • requirements engineeringsoftware code • software design principles • software design problems • software developmentsoftware engineeringsoftware modellingsoftware programmingsoftware requirementssoftware tutorial • subclass • superclass • UML • UML diagram • Unified Modelling Languagevideo tutorial

CONTRIBUTOR

Simon Perkins
25 SEPTEMBER 2013

Ladies Learning Code: promoting a diverse workforce

"Ladies Learning Code is a Toronto–based not–for–profit organization that runs workshops for women (and men) who want to learn beginner–friendly computer programming and other technical skills in a social and collaborative way. Today we have chapters across Canada, a thriving girls' program called Girls Learning Code and a permanent workshop space in Toronto. Oh, and we're just getting started."

1
2
3

TAGS

beginner-friendlyCanadacode clubcollaborative learningcomputer programmerscomputer programmingcomputer programming education • diverse teams • diverse workforce • gendered technology • Girls Learning Code (workshop) • girls programme • Heather Payne • Ladies Learning Code (workshop) • learn to codelearning softwarenot for profitsocial learningsoftware developerssoftware developmentsoftware literacySTEM subjects • technical skills • technology educationTorontowomenwomen and technologywomen in technologyworkshop for womenworkshops

CONTRIBUTOR

Simon Perkins
09 DECEMBER 2012

IAMAS 情報科学芸術大学院大学 / Institute of Advanced Media Arts and Sciences

"Cultivating new media creators in a variety of fields IAMAS was opened in 2001 both as a hub for training new creators in an information society, and as an educational institution that fuses together advanced technology and artistic creativity to produce new culture. Since then IAMAS has graduated a large number of information technology specialists who are active in the broad field of media culture and industry, garnering high praise not just in Japan, but internationally as well. The school's activities cover many disciplines and offer new possibilities to industry. These activities include interaction design and media products that lead to collaboration with industry, media art that constantly explores new methods of expression, social research and design, as well as new publishing ideas. All of these endeavors exemplify the spirit of pioneering into new fields. The Department of Media Creation at IAMAS is a place where people with the desire to create something new are able to meet, collaborate, and challenge each other."

1

TAGS

2001 • advanced technology • art and designcreative industry • diverse faculty • education and research • hands-on facilities • IAMAS • IAMAS Media Lab • industry collaboration • information society • information technology specialists • innovative media • Institute of Advanced Media Arts and Sciences • interaction designinterdisciplinary thinkingJapan • joint research • media art • media culture industry • new culture • new fields • new methods of expression • new publishing • prototyping lab • research and design • social research • Softopia Japan • software development • The Department of Media Creation • the future of society • unique curriculum • visual studio

CONTRIBUTOR

Simon Perkins
17 JUNE 2011

GitHub, Collaboration, and Haters

"You've probably all seen the article on RWW yesterday about GitHub surpassing SF.net, GoogleCode, and Codeplex. Kudos to our friends at GitHub! They've had some great ideas and have executed them flawlessly. They have made Git the number one VCS used by software devs. Most importantly, they have helped open source grow, and helped open source projects be more successful, and really that's all we care about. Many people use us together; GitHub for collaboration, and SF.net for distribution, since our end–user interface is a little more friendly to the non–techies. Really it just comes down to using whatever tools work best for you and your team, and we totally understand that. So from SF to GitHub– High five! ...

Open source is all about choice, transparency, and collaboration, not hating on others. Use what tools work best for you, and respect that others may choose a different path."

(SourceForge Community Blog)

TAGS

2011 • Black Duck • CodePlex • constructive feedback • downloadable projects • GitHub • Google Code • haters • hating on us • metricsno single standardopen sourceopen source communityopen source filesopen source platform • open source projects • opinionpopular votepopularity • popularity contest • project-sharing website • ReadWrite (news) • ReadWriteWeb (news) • Redmonk (site) • relevance • RWW • software development • software version control • SourceForgeusage • usage analysis • user preferences • VCS • version control • version control system

CONTRIBUTOR

Simon Perkins
Sign-In

Sign-In to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.