Ken Schwaber and Jeff Sutherland wrote The Scrum Guide as manifesto for Scrum.org. It is there view on how to approach agile projects.
The document is very concise and explains scrum in all it aspects:
But don’t be mistaken it is not because the theory is easy to understand, Scrum is simple to apply and to master.
More info on:
“The Lean Startup” by Eric Ries is organized around 5 principles:
A startup is an experiment under extreme uncertainty. Most startup fails and often only the success stories make the news.
Lean startups must be managed differently. Classical management skills fail because they do not take into account the level of uncertainty in startups General management skills do not work for the two guys in the garage. Startups survive because they pivot fast: use a foundation, adapt quickly to circumstances and apply the lessons learned. Startups win through the speed they can adapt and before they run out of money.
Failures are successfully executed bad plans. You achieved to deliver on time, budget and with the correct quality something nobody wants.
To avoid the failure trap feedback cycles must go fast and must be iterate multiple times “Release early and release often”:
Build should focus on a Minimum Viable Product (MVP). The MVP is put in front of customers as a kind of experiment and measured.
Measurements must be tripe A: Actionable, accessible and auditable. The measurements are used to tweak and improve the MVP. If the cycles show diminishing returns it is time to pivot or change the game plan.
“The One Minute Manager “ by Kenneth Blanchard and Spencer Johnson explain management according to a set of one minute tasks.
“People who feel good about themselves produce good results.”
“Help reach people their full potential. Catch them doing something right.”
“The best minute I spend is the one I invest in people.”
“Everyone is a potential winner. Some people are disguised as losers. Don’t let their appearances fool you.”
“Take a minute to look at your goals. Look at your performance. See if you behavior matches your goals.”
“We are not just our behavior. We are the person managing our behavior.”
“Goals begin behaviors. Consequences maintain behaviors.”
“The Web Application Hacker’s Handbook” by Dafydd Stuttard and Marcus Pinto.
The book was written already in 2008 but points out many, still to date, common security risks that every developer should know about. Security is for most either a developers a nightmare – it is my job but I have clue – or either an afterthought – this is not my job.
The book covers many ways your custom build website is at risk, some examples
Confidentiality
Integrity
Authentication
Authorization
Non-repudiation
Availability
More details in the following overview slide deck: